When apps run fine on one machine and not on another, or run fine in one version and not when run under a newer version, one the first thing you have to think about are Missing References, and it could be the source of your problem, here.
If you haven't checked for this kind of thing before, here are Doug Steele's detailed instructions on how to troubleshoot the problem:
Access Reference Problems
And while this could be a matter as simple as a Missing Reference, you really have a far greater problem, here:
Originally Posted by
NISMOJim
...As for this database, it is all in one (not split design if I understand that right), and is on a shared drive, so everyone has access to it...
To be absolutely blunt about this, you are probably wasting your time trying to trouble-shoot this problem until you Split this database into a Front End/Back End configuration as is required on all Multi-User Access apps!
Having multiple users sharing a single, non-split database, sitting on a network drive, is the sure way to repeated episodes of corruption, as well as speed and timing problems, all of which can present as Compilation errors! Multiple users simply have to work off of a Split Database, with each user having their own copy of the Front End, which contains everything except the data/tables, on their respective hard drives, and a Back End with all Tables on a shared drive.
Being in forced retirement, I spend 6-8 hours a day here, and on other Access forums/newsgroups, and over the past six years have literally seen hundreds of reports similar to yours! The really insidious thing is that the app can work for extended periods of time before the troubles begin! But once it does, they become chronic, which is to say they occur over and over and over again!
Without having a Split app, here, you're facing the certainty that, sooner or later, you're going to face much more than Compilation Errors, you're going to be facing corruption and the possible lose of data!
Linq ;0)>
The problem with making anything foolproof...is that fools are so darn ingenious!
All posts/responses based on Access 2003/2007