Question Huge networking mystery!

[jlm722]

OK folks, i know this is going to sound completely crazy. Please allow me to give a little background. I have an access 2000 database that is split front end/back end. I used to be able to work with this database from several different computers at a time in my office. However, something changed recently. My files are located on the c: drive, in a folder called "databases", with a subfolder called "business name". I can double click on any file in this folder (jpg, wav, doc, etc) and run the file perfect. I have a file called CheckData.mdb which is the back end file containing the info i need. If I click on this file, i get the error "microsoft access can't find the file blah blah blah" THIS is where it gets tricky!!! If I go to the computer where the file is stored and rename the file to anything else example: Sunny.mdb, it will open perfectly! So can someone tell me WHY when this file has the name CheckData.mdb, will it not open??? There HAS to be an explanation for this! I am about to pull my hair out!

 

[georgedwilkinson]

Hmmm. Curious.

It's hard to troubleshoot this type of thing when you're possibly several thousand miles away. I just wonder what else is in that directory? Any LDF files?

And if I understand you correctly, you're opening the back end? Why?

 

[gemma-the-husky]

I have a file called CheckData.mdb which is the back end file containing the info i need. If I click on this file, i get the error "microsoft access can't find the file blah blah blah" THIS is where it gets tricky!!! If I go to the computer where the file is stored and rename the file to anything else example: Sunny.mdb, it will open perfectly!

the way you put it, it sounds like the backendfile in your C drive is a short cut or hyperlink to the real back end file

so maybe the short cut is broken?, or something like that

 

[WayneRyan]

jlm,

When you rename the file, do you also relink the tables in your front-end?

What happens if you try to import files from the CheckData.mdb file?

What happens if you try to open the DB with the shift key down?

After the rename, how are you invoking it to get it to successfully open?

What are the connection properties for the *valid* front-ends?

Wayne

 

[jlm722]

ok, I always hate when someone posts topics out here and don't give ALL the details needed, and here I found myself doing the same. Let me explain better this time.
I had someone more knowledgeable than me create a database using access 2000. This database worked like a charm. I have a main office computer that gets most of the work, but occasionally, we need the use of a second computer when it gets busy. At one time, I could do this perfectly. However, the person who created this database has vanished. I know just enough about access to be dangerous. There were some minor fixes (reports needed extra wording etc.) I had to make within the database. Now I can no longer link the front-end mdb on the “second” computer to the back-end mdb on that “main” computer. On the “second” computer, I have a mapped network drive “Z” that points to the folder in which the file “CheckData.mdb” is located on the “main” computer. When I do the “File-Get External Data-Link Tables-Look in-yada yada” I get the all too familiar error: The Microsoft Jet database engine cannot open the file ‘Z:\CheckData.mdb’. It is already opened exclusively by another user, or you need permission to view its data. I promise! I have read and read on this matter. It is NOT opened exclusively by another, and I HAVE permission! To the best of my knowledge, I haven’t changed any thing dealing with that! The mystery that I can not solve is, (I found this by accident) if I rename the file CheckData.mdb to something else like elephant.mdb, it will link! WHY IS THIS? I am SOOO lost! Please help!

 

[gemma-the-husky]

3 thoughts

it is called "checkdata.MDB" isnt it -

a) theres not an embedded space in it, is there?
b) maybe you're getting caught by 8.3 file names
and checkdata is realy being stored as checkd~1.mdb, or something daft like that.
c) try using fully specified path
"\\mymachine\data_area1\checkdata.mdb"

 

[The_Doc_Man]

If there is a "dangling" CheckData.LDB file, delete it when no one can possibly be in the database. If that file has been created and is locked, that would do it.

Renaming the .MDB implicitly renames the .LDB file when you next open the DB so you avoid the conflict.

 

[dfenton]

You may also need to check the permissions on both the folder on the machine acting as server and on the share defined for that folder.

Also, on the "server" go to Control Panel | Administrative Tools | Computer Management, and then select Shared Folders and then Open Files. Perhaps there is a file lock left on either the MDB or LDB. You can find out what user has the lock and then have that user log off their Windows session, which should then release the lock.

It's not a good idea to force close a lock on an MDB file because this can corrupt the MDB, but if all else fails, you can make a backup and the force close the open file handle.

 

[jlm722]

Folks, thanks very much! I'm going to try all of your suggestions! This has been absolutely about to drive me insane! I have tried EVERYTHING. I'll reply back and let ya know if I have any luck.

 

[jlm722]

So, let me ask this question. If somehow, while copying the mdb file etc. Back when I was making changes, I caused the file to become corrupted by copying while open or similiar, Is there a way to repair this corruption? I'm thinking now this is what happened. This would explain why I can link to the "old" mdb before I made changes, but can't link to it now.

 

[gemma-the-husky]

normal way is to open a new dbs, and import everything from the old one

always a good idea to save a tested, working but otherwise unused copy of each vcersion of your dbs - for reasons like this

 

[jlm722]

gemma-the-husky, YOU my friend are my HERO!!! I did what you said about opening a new mdb and imported the tables from the one that wasn't working. I renamed the new one to what I needed (CheckData. mdb) it works perfect! Thank you! Thank you! Thank you!

 

[gemma-the-husky]

glad you got it sorted - corruption is a "creeping thing" - you dont realise its there until odd things start happening - and you dont immediately thing it is a corrupted db. sometimes you can get the stuff out, but sometimes it gets worse and you can't - its important to have a safe backup