Changing Table yields "too many fields" error

[dj]

I am implementing (what a dreamer) a multi-table db. One of the tables had 18 fields in it and a little logic suggested I split it into 2 tables. In attempting to delete fields from the table, I kept getting the message above.(256 fields is max) It would not save any changes, therefore I'm hooped. (of course I could delete the entire table and start over) Seems to be the trademark of all MS software. Trouble is when I did that, a 10 field table produced the same message. (using MS Access 2000) So I went looking in this Labyrinth they call a website for answers. I found one that proposed a 'try this and see if it works' typical MS solution. What a joke. Also found out that the same bug is in version 2003. Don't they ever fix documented problems?
Has anyone got a solution other than their condescending BS? I can't imagine with the volume of bugs they have in this crap that any serious business anywhere would take a chance with any of their software. We have certainly changed our plans as a result of the COMPLETE unreliability of Access. We're going back to Punched Cards.
Forgive my venting, but maybe if more people did, the message may register with that outfit and they can go back to selling pencils. They are a perfect example of the "Peter Principle" at a corporate level.

 

[Jeff Boyce]

Have you run the Compact and Repair utility?

Does this happen with every one of your .MDBs or just the one?

Is your database "split"?

Which version of Access?

More info, please ...

Jeff Boyce
<Access MVP>

 

[Guest]

Thanks Jeff,
This is the 3rd db I've done with Access 2000. I classify
them as Mickey Mouse. The error happened on a three table
db when I went back to change some field
properties. 'Split'? Don't know. It's the first time I
had the problem. It is documented but I am after a fix as
all they suggest is to compact, copy, rename etc etc. Bit
of a 'Bandaid approach'. Keeps people employed though.
Appreciated.