Sparx Systems Forum
Enterprise Architect => General Board => Topic started by: Jan van Mastbergen on January 21, 2007, 02:05:11 pm
-
I am trying to import a .xmi file from another tool into a .eap file. Apart from the usual nastyness due to uml/xmi version differences it is giving me this:
DAO.Field[3163] The field is too small to accept the amount of data you attempted to add. Try...
And that's all. The failure does not show up in the log file. How can I figure out which is the field that is too small? After that I should be able to find the element in the .xmi that is too long.
TIA, Jan
-
Hi Jan,
This is a difficult one due to EA's lack of effective instrumentation in this area.
We've encountered field length too small problems from time to time.
If your text editor can do it, look for entries with a value greater than 255 characters (that is, between the ">" and "<" ), that are NOT already memo fields in the .EAP file.
HTH (but I doubt it),
Paolo
PS: If your text editor can't do it, download UltraEdit (http://www.ultraedit.com/index.php) for a trial (and use its Pearl Regular expression facility)
-
A bit of a hack (but a useful one)....
Increase the size of your fields in the database (say to 4000 chars - or switch to text fields if an EAP). Try t_object.note
and t_objectproperties.value, t_attributetag.value and t_connectortag.value (if your model has tagged values on an extended stereotype)
Otherwise, there must be some sort of DAO level trace you can enable so you can see which SQL is failing... don't know how though....
Cheers,
DAvid.
-
Otherwise, there must be some sort of DAO level trace you can enable so you can see which SQL is failing... don't know how though....
If you can send your XMI to [email protected] then we can figure out where it's going wrong for you (and improve the error recovery and error message while we're at it).
-
Thnkx, will do. Jan