ArgumentOutOfRangeException: The value specified will cause an overflow error in the database. Value length: 16. Column max. length: 10 Parameter name: Type

I do not understand why i am getting this exception thrown. My database has the field as nvarchar(30)

LLBL project designer sees it as that type of field when I edit the properties for the specified table.

I have regenerated the code, rebuilt the db specific and non specific projects and added the correct bins to my website bin folder??

kWhat else do I need to do?

Like you, I'm an end user. It would be helpful if you used the posting guidelines at http://www.llblgen.com/TinyForum/Messages.aspx?ThreadID=7720

Have you restarted the web server?

Have you checked the web.config connection string to ensure that it is connecting to the same database as that used to refresh the designer?

I've had the same issues, and the above steps helped me.

Hello,

what version of llblgen do you use? when did this error come(when trying to upgrade a field, saving an entity ..)?

Have you restarted the web server? Yes, several times since the cahnge occured on the db.

Have you checked the web.config connection string to ensure that it is connecting to the same database as that used to refresh the designer? I have three db's that my code generated points too. I am pointing to the XML Appconfig file created.

what version of llblgen do you use? Version 2.0

when did this error come(when trying to upgrade a field, saving an entity ..)? The error occurs when updating an entity.

About three days ago I changed the status field to accept length 30. One day ago I added workingrrid and oldstatus to another table same db. I regenerated the code. rebuilt the vb projects. I have access to the new fields. But the status field still gives me the problem. Do I need to temporarily get rid of the collumn in the db? Very odd.

I guess your application somehow is using an older version of the generated code. Make sure the application reference the most recent version of the genareted code.

I have regenerated the code, rebuilt the db specific and non specific projects and added the correct bins to my website bin folder??

Sometimes bins from the ASP.NET temp folder or the gac can be still used rather than the new bins, so make sure you delete any previous existing version of your generated code (DBSpecific & DBGeneric)

I have the exact same problem... So what is the solution to this problem... ?

MichaelLeppan wrote:

I have the exact same problem... So what is the solution to this problem... ?

Have you checked Walaa's post right above yours?

I would like to add, if you are using this product in a team environment, make sure no other team members have deleted constraints or foreign keys...