Question Database corrupts when any changes are made

[BRABUS]

Hi there,

I am really pulling my hair out here. I have a database that I use and normally I dont have any problems. For some reason all of a sudden if I make any changes to the structure it errors and asks me if I want to fix the database.

Entering data and running reports is fine. If I add new tables or edit the structure of exisiting tables etc then I get this error every time. If I copy the databse to another machine it runs fine, but as soon as I try to make changes once again it errors.

I have done a full scan of my machine just to be certain there are no infections etc and its all clean.

I am running Access 2003 (11.8166.8221) SP3 on an XP Pro machine also with SP3 installed.

Can any one help please.

 

[Trevor G]

Would you be able to upload a stripped down version?

Just a thought you haven't made it an mde database have you!

 

[BRABUS]

hi thanks for the quick reply.

unfortunately as it contains MOD data even if I deleted the data I could be sacked for posting it up.

A few points though, the database is a single entity and is not split into FE and BE components.

The database structure has not changed for months.

 

[Trevor G]

Only other thing I can suggest without seeing the database is to check the references in the VBA screen to see if anything is missing.

Use Alt + F11 on the keyboard then look at the Tools Menu and References, if anything is missing it will show from the list of selected items? Last thought do multiple users use the database and do you have different versions of MS Office as this will give you problems.

 

[BRABUS]

Yes multiple uses do use the database but everyone has exactly the same buld of pc and they are locked down so they cant fiddle with them.

I will try the F11 trick now.

 

[DCrake]

If everyone has their own copy of the database then how do users share the data they are using? Anyway even if it is a standalone mdb I would still split it BE FE.

 

[JamesMcS]

I've had a database pack up before, after a bit of googling I found that the way to fix it was to import everything individually into a fresh MDB - not all in one go though. I'm not sure what the difference is to be honest but it worked for me.....