Back to my question about breaking up a table that is too large.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I tried it the way you said and it didn't work for me...just me I'm sure.
However, I went to table design and deleted certain fields to later put in
another field. When I tried to save the existing table, it says I have "Too
Many fields" ...more than 255. This is not so, I deleted several fields
from what I had before. what's happening?
 
Rich said:
I tried it the way you said and it didn't work for me...just me I'm
sure. However, I went to table design and deleted certain fields to
later put in another field. When I tried to save the existing table,
it says I have "Too Many fields" ...more than 255. This is not so,
I deleted several fields from what I had before. what's happening?

I believe you need to do a compact (under Tools, Database Utilities)
before they really disappear and you get the memory back.
 
I tried it the way you said and it didn't work for me...just me I'm sure.
However, I went to table design and deleted certain fields to later put in
another field. When I tried to save the existing table, it says I have "Too
Many fields" ...more than 255. This is not so, I deleted several fields
from what I had before. what's happening?

As Joseph says, you need to use Tools... Database Utilities... Compact
and Repair. Each time you add - or even change the definition of - a
field, one of the 255 "slots" gets used up. Deleting the field doesn't
free up the slot; it's recovered only when you Compact.

If your resulting table has more than 50 or 60 fields, it's very
likely still MUCH too wide, and needs normalization. Is that what
you're trying to accomplish - I hope!?

John W. Vinson[MVP]
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top