DAO errors when reverse engineering EntLib 4.0

[Brad Hehe]

I keep getting several DAO errors when trying to reverse engineer Enterprise Library 4.0....  It seems there is some piece of data discovered through the disassembly (it kept saying reflection failed so I guess it deferred to the other means of reverse engineering an assembly) that the database model can not store due to a size issue...

DAO.Field[3163]

The field is too small to accept the amount of data you attempted to add.  Try inserting or pasting less data.

The 1st instance hits when the progress window says it is "Adding: Class - CacheManagerSettings"...

So my 2 questions are this...

Did that botch my reverse engineering and can I count on the reliability of what was imported?

Is there a fix/workaround or is this just a bug? Can I hack the data model to increase something (i.e. say there is a VARBINARY(2048) column and could I make it VARBINARY(MAX) to get around this)?

[Brad Hehe]

From what I can tell, my model looks basically correct - but I have no means of really verifying what was or was not imported due to this bug/error message...

I'd still like to know more but I think I can work with what I have imported. Hopefully this is something addressed in the future.

[«Midnight»]

First, make sure you are using the most recent build of EA - 832 at this time - so that your schema is not out of date. You might also want to ensure that you've done a full installation, since the patch files might have left an out of date EABase project around.

If you're up to date, I suggest you report this to Sparx Support. The problem might indicate a problem with the schema, what EA is attempting to put in the schema, or something missing in the sanity checks before EA attempts to store data.

David