Can't Link tables on another pc 1

[cubstyled]

I have a mailinglist.mdb that i need to link to a customermaster.mdb on another machine. every time i try this i get a ..."The Microsoft Jet database engine cannot open the file <name>. It is already opened exclusively by another user, or you need permission to view its data. I have supervisor rights throughout (GOD), i have even checked and double checked the security on the database and on all the machines involved.
Currently I have about 5 mdb allready linked to the customermaster.mdb with now trouble ( they all are on the same machine, no drive mapping just c but when i try to map to the mdb whether by dirve mapping ( y or by unc, i get the same error. I also can't even open the mdb remotely. I am limited to where the customermaster.mdb is located becasue of size (1.4g) and speed. All machines are running xpsp1 and one of the files is on a novell serever, but even putting them on the same XP machine i get the same results.
I have aslo checked to see if the idb is being deleted when the db is closed and it is.

This has been driving me nuts! Any help would be greatly appreciated!!!!

 

[HitechUser]

cubstyled,

You must be really stressed. Your post has many missspelled words. Let's see if we can help.

There are two things that come to mind.

1.) Does the remote user have sufficent authority (permissions) to the directory where the MDB resides??

2.) Is the Open Exclusively set incorrectly for the remote MDB?? Use Tools > Options > Advanced to check/change.

Let me know..

 

[cubstyled]

HitechUser
the word stressed doesn't even begin to describe it!
Yes, all of the flags are set to shared and not exclusive, as far as rights go, I am using my credetials (wide open throughout) and they have been checked and re-checked. I can browse to the directory \\D5v13221crdell\Paragon\DataWarehouse
and see all the files. I can open all of the mdb's there except the ones that are connected to the customermaster.mdb with the exception of one, and I have no clue why I can open that one and not the others ( all of the tables in this one as with most of the others are linked)
thanks

 

[HitechUser]

Sometime Access get hosed!!! So please try this..

From the remote machine (you) create an empty MDB on the local machine. Then have the local user open your new MDB and the import EVERYTHING from the problem MDB. Now (local user) renames the original MDB to xxxSave.mdb. Make sure the are NO LDB's left. Now rename your newly created MDB to the original name. Now try your remote connection.

There are many times where I have seen some corruption (compress and repair do not fix) that I have only been able to "fix" by "starting" fresh..

Let me know...

 

[cubstyled]

I am giving that a shot as we speak, I will get back and let you know. It will probably take a while 1.4gigs

 

[cubstyled]

HitechUser
It worked!!
THANK YOU THANK YOU THANK YOU!
you have been given my star