Access references change - Help!

[SJG0526]

My Access 97 db is running fine on a Win95 pc however when another user tries to run it on a different pc in Win2K, they have to go in and reset the references. Then when it is run again on the Win95 pc, the references are screwed up and must be reset there too. In other words, a W2K pc and a Win95 pc can not run the same database without resetting the references each time. What am I missing here??

TIA!

 

[GDGarth]

I don't know why your references keep changing, but here's one thing you may be able to do to fix it:

Is your database split (front end on local machine, back end on server)? If not, you should do so. It will be more stable - much less likely to get corrupted.

Go to "Tools", "Addins" and choose "Database Splitter". This will split your database into two. You can then give each user their own copy of the database that contains the interface (the data is still on the server). That way, if it changes their references, it's no big deal.

If you make changes, just send them a new copy of the front end - since there's no data there, it will work just fine.

 

[SJG0526]

The W2k pcs have Access 97 and Access 2000 on them. Could this be causing a problem?

Thanks for the suggestion on splitting the database. I may just do that. I assume, then that the references are stored in the database, not the pc's registry, right? If so, then when you look at the reference listing, does it just add in available references on that particular pc?

Thanks!

 

[GDGarth]

If you're running two different versions of Access, I'm sure that's what's causing the problem. I think (but I'm not sure), that the references are contained in the database. I'm a long way from an expert on references......

I really think you'll have to split it to have users with different versions of Access. I think that's the real source of your problem.

 

[spider8]

Maybe your lowest DAO reference library on win2k is still higher than your higest DAO reference library on Win95? You could either install a lower reference on win 2k (we did something like that, but it was actually on an NT, not win2k), or go with different front ends, as suggested...I had to have DAO 3.5 installed(in the Microsoft Shared folder)once, in order to get a common DAO version running for my users....

 

[Lightning]

The W2k pcs have Access 97 and Access 2000 on them. Could this be causing a problem?

Running two different versions of Access on the one machine will not cause any problems, provided

The versions are in different folders; and

The versions were installed in order
Access 97 first
Access 2000 second

I run three versions of Access on my PC and have never had any version conflicts/problems.

I assume, then that the references are stored in the database, not the pc's registry, right?

Yes, the references are stored within the database. In this way, different databases on the same machine can all have different references without affecting each other.

GDGarth's suggestion of splitting the database is the solution to your problem (as well as a number of others that can/will occur with a multi-user database).

Split the database, give each user their own copy of the Front-End (Forms, Queries, Reports, etc) and leave the Back-end (Tables only) on the server. Then set the references required for each user. End of problem.

HTH
Lightning