M
mark R.
I took some advice I recently received (several times) and
identified about 35 fields out of 215 that I
could "normalize" and put into another table (out of my
original table), utilizing subform with those 35.
I needed to replacce those 35 fields with 10 new ones (a
savings of 25 fields).
I used the delete rows right click and deleted those 35
fields. Then when I went to add one (my total is now les
than 180 fields) I got an error , too many fields.
I knew this was not true, so I investigated field by
field. To make a long story a little short, I eventually
found that if I deleted one particular field named "K_",
I no longer got the error message. I have since added 45
fields and still no problem.
Should I assume ACCESS fixed the problem, or after my
prototype is finished, should I delete the whole test
table and retype it in from scratch, with no data in it at
all, and start the actual live beta test with a fresh
table?
identified about 35 fields out of 215 that I
could "normalize" and put into another table (out of my
original table), utilizing subform with those 35.
I needed to replacce those 35 fields with 10 new ones (a
savings of 25 fields).
I used the delete rows right click and deleted those 35
fields. Then when I went to add one (my total is now les
than 180 fields) I got an error , too many fields.
I knew this was not true, so I investigated field by
field. To make a long story a little short, I eventually
found that if I deleted one particular field named "K_",
I no longer got the error message. I have since added 45
fields and still no problem.
Should I assume ACCESS fixed the problem, or after my
prototype is finished, should I delete the whole test
table and retype it in from scratch, with no data in it at
all, and start the actual live beta test with a fresh
table?