Property Value is too large

[Ledmark]

I built a table in a datatbase with macros performing calculations and everything was working fine. I haven't gone ito the database for a few weeks to work on it and today I went in to just look at the table, added a field, then decided not to add it and deleted it so it was just the same as before. When I went to save it a box popped up indicating "Property Value Is Too Large" and I have no idea why it would do that. Can someone tell me what property value it's referring to and how I might fix it?

Thank you
Laura

[Lysander]

I built a table in a datatbase with macros performing calculations and everything was working fine. I haven't gone ito the database for a few weeks to work on it and today I went in to just look at the table, added a field, then decided not to add it and deleted it so it was just the same as before. When I went to save it a box popped up indicating "Property Value Is Too Large" and I have no idea why it would do that. Can someone tell me what property value it's referring to and how I might fix it?

Thank you
Laura

I get that when I try to add more than 255 fields to a table. Sometimes access allows it, but then when you go to edit the table, you get this weird, property value is too large, error. You should keep the number of fields in a table less than 255. (I also get the same error if I have too many relationships on a table, but can't remember of the top of my head what the limit is)

[missinglinq]

The specs can be found at Microsoft Access Specifications. Research indicates that trying to stuff too much into a table is, indeed, the reason behind this error. And as Lysander indicated, it's not as simple as trying to add more than 255 fields to a table! Other table limits and combinations of limits apparently come into play, such as how many indexes are present, how many fields per indexes, etc. I've seen reports of the problem where only 100 fields were present!

The prevailing thought in the database community is that tables having more than 25 or 30 fields is an indication of poor design where normalization is absent. You probably need to give some thought to redesigning your app.

Having said that, my best guess for getting your app back up and running in its current configuration would be to create a blank database and import all objects into it. The problem with Acesss and its limits is that once something is added, such as a control to a form or a field to a table, it's counted against the limit, even if it's later deleted! I think doing the new DB/Import all objects huckabuck will reset these limits for the time being.

Welcome to TheScripts!

Linq ;0):>