I am having a peculiar problem with Access (2003). The database is a meager 4mbs in size and I use several forms to access my tables. Recently I found a need to add more columns (currency data) to one of my tables. So when I did, then tried to open my one of my forms, Access says 'MS Access has encountered an error and needs to close...' If I remove the recently added column in that table, all is well--no crashes. I've tried this a number of times and it gives me the same exact results every time. Adding a column to a certain table, then open form--crash. Remove column from that table--all is well.

Has anyone experienced this problem before?

Access goes wacky from time to time. The generic suggestion is to try compact & repair. Then if that doesn't help try copying everything over into a new database.

open your form in design mode - add the extra field and then see what happens

is your form based on a qry or a table ??

Wow--quick responses! The forms are based on a combo box selection/query. Select something from the combo box and the form populates it with the rest of the record data.

I'll try adding the newly added columns as items on the form and see what that does.

Okay, MS Access crashes even when I attempt to open the form up in Design view! What next?

May we assume you tried repairing the db?

Oh yes, I've already done that. I also set a stop on the first line of the 'form load' code event in vb just to see if it makes it that far. It doesn't.

And have you tried copying all of the objects over into a new .mdb?

I think I tried that back when I first had this problem. Oh--at the suggestion of someone else I also split the database into two dbs--a front end and a backend db.

This problem is bizarre--I just deleted the new extra columns from the table and everything is fine now--no crashes when I launch the particular form. But I need to add more data! :)

Can you post a sample db?

Maybe--I'm still looking into this; I just re-added the columns again and can't seem to make it crash now. It may have something to do with actually having data in those columns, which is what I will be doing here shortly.

I had a similar problem, rebuilding the object fixed it. It wasn't an error with my access .mdb. Just that particular object. I think the underlying coding became corrupt.

Maybe--I'm still looking into this; I just re-added the columns again and can't seem to make it crash now. It may have something to do with actually having data in those columns, which is what I will be doing here shortly.

Okay, me and one of my IT guys just determined this--whenever I add a 27th column to a certain table, it crashes (when I launch the particular form). Is there some limit with forms or combo boxes that relates to columns in a referenced or bound table?

26 columns sounds alphabetic realted

you're not trying to do something with the table that would although A to Z refs, but nothing higher, are you?

access limit is 255 columns I think, so it isnt the physical size

No, not doing anything of that nature.

it could be your combo box colomns are out by one .. espically if theres a required field in there somewhere - but you are into t he realms where I have to bail out and leave it to the pro's

as an after thought .. are you using the after update fuction in a combo or dlookup ?

I want a copy of the suspect db to tinker with - :)

I do not know toooo much about Access but I would try to create a new access file and copy and paste everything into it. Like a new MDB or ACCDB :)