-
Too many fields defined
I just added 6 more fields to one of my tables to make a total of 22 fields in this table. When I try to edit my form to add these fields, it tells me "too many fields defined." This table is linked to another table that does not have more than 215. What should I do? I can't delete fields from the other table or I would lose data.
-
I don't have a short term solution for ya besides suggesting using the table analyzer to chop things up, but I would highly recommend reading up on normalization. http://support.microsoft.com/default...b;en-us;100139
-
Just a thought on something you might try. I had this happen to me and it worked. I created a new form in design vew and did select all and a copy and paste from the old form to the new one and it solved the problem. Remember to relink to the same record source when you thry this. No promises, just an idea.
Gary
-
Access has a memory for fields added and later removed. I can't remember all the details, but try comressing the database to clear it.
-
I tried doing the analyzer first and I got all the way to the end and it says "File sharing lock count exceeded. Increase MaxLocksPerFile registry entry."
Never seen this before.
-
The default max is 9500. If you were doing this in code, then it would be easier to change, but you'll need to go into your registry and increase the value (if you want to use the table analyzer).
http://support.microsoft.com/default.aspx?id=815281
-
Ok i changed it to 15000 but it still gives me the error.
It would be so nice to be able to split the main table into smaller ones.
-
15000 isn't high enough then. Try 200000.
-
Will this actually remove the data from the main table and replace it into a new table?
-
Yes, it removes fields and their corresponding data from a table and inserts them into another then links via a key. I can't remember if it creates a backup or not, so be sure you're working with a version that you can mess up.
-
I'm still getting the error -too many fields defined. I've tried all three solutions in this post.
-
And I have to change all queries to change the source to the new tables and I get the error "the setting for the LIstRows property must be from 1 through 255."
-
Were you able to split your tables or not?
-
-
Sorry - I gave up. It split it but nothing was linked so I had to go back to the original table.
-
You're best bet would be to tackle it programmatically then, if normalizing is something you deem necessary. Did you check out the first article I linked to?