Compile error

[NISMOJim]

Hello,
One of my users is getting a compile error on a field with the following code;

Private Sub txtLocation_AfterUpdate ()


Me.txtLocation = StrConv (Me.txtLocation, vbUpperCase)
End Sub

The window says Microsoft Visual Basic
Compile Error:
Can't find project or library.

We're using Access 2007. While one user is getting this error, everything works fine on a different computer for other users. I'm thinking that something needs to be checked in the reference library on his computer, but I thought the references were accessed through the database, not the Access program for each computer. Does someone know for sure how this works, and if it is the case, which library should be checked to make this code work?

Thank you for any insight into what's going on.

[June7]

The library selections are file specific, not an application setting.

This is a split design? Are you sure user has the same version of frontend as everyone else? Have you tried replacing user's copy?

[NISMOJim]

By file specific, does that mean the reference libraries that are checked must be checked on each computer that uses this database?
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. Everything works on the other computers in the warehouse, just his computer is getting the error.

[June7]

No, I mean you were correct, the libraries selected is a setting of the db. Library selections are not an application setting.

However, just hit me the error is Access is not finding the library. If Access application is not finding the selected library, then sounds like that install is corrupt. Try reinstalling Access.

If necessary library was not even selected the error message would be different.

[NISMOJim]

Thanks, I'll have him try that in the morning. That makes sense, because I'm pretty sure it must have worked for him before today.

[Missinglinq]

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:

...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)>