XP problem. Linking tables to more than one mdb. HELP

[Guest]

I have a split db. All but two of the tables are in a backend db. The other
two tables are in a different mdb (OwnerDog.mdb). In the frontend, I linked
the tables to the backend and linked the other two tables (Owner and Dog) to
the other mdb (OwnerDog.mdb).

What am I missing with the XP Professional and Access that it does not like
the frontend to have tables linked to more than one mdb?

All worked well accross a network using 2000 Professional and 98 2nd
edition. I now have a HP laptop with XPprofessional and went thru lots of
problems getting the other comuters to access the Owner and Dog table in
OwnerDog.mdb on that new Laptop It would work ok for the other tables -
could open them fine. But not two tables linked to OwnerDog.mdb.

When I mapped the XP machine's Cdrive to S drive (shared of course and Guest
account turned on the XP machine) and tried to open the OwnerDog.mdb on the
XP machine from the 2000P machine - I got the following message "Microsoft
Access can't find the databse file "S:\FT\AAdata\OwnerDog.mdb". Make sure
you entered the current path and file name." But I can open the backend db
fine that has all the other tables.

If I start the front end from the 2000P machine(that has been linked to S
drive (the XP machine) I get: The Microsoft Jet Database cannot open the file
'S:\FT\AAdata\OwnerDog.mdb'. It is already opened exclusively by another user
or you need permission to view its data.

Now to make matter worse - somehow the HP Laptop is now working fine with
the others on the network and the other new Dell XP professional machine that
I just hooked up is now doing the same problem. I did a windows update on
the Dell XP machine but still the same problem.

WHat am I missing????? HELPPPPPPPPP

 

[Douglas J. Steele]

There are no problems that I'm aware of linking to multiple data sources.

Are you certain that you've got the correct path to the backend? Are you
certain that your userid has the appropriate permissions on the folder where
the backend database exists (you need Change, or Read, Write, eXecute and
Delete)?