Front / Back end Problem

[MHadden]

I have a DB (Access 2000) that is split into front / back end. The problem I have is that if the program is open on one computer, you can't open it on the other one. Oddly enough, if you open it on the second computer first, you can then open it on the first one with no problem. I have checked to ensure that all have been set to open "shared" rather then exclusive, and I don't know what to try next.
Any help would be appreciated.
Thanks - in - Advance,
Michael MHadden#knology.net
If you give someone a fish, you have given them a meal. If you teach someone to fish, you have given them MANY meals!

 

[thornmastr]

Michael,

A few questions. Your back end is sitting on the network. You have a copy of your front end on each users PC. You don’t have just one copy of the FE on the network and your users all access it. If you do, change it. That is a known cause of corruption and generates tremendous, unnecessary network traffic.

Check the permissions your users have to the folder where your BE resides.
Robert Berman
Data Base consultant
Vulcan Software Services
thornmastr@yahoo.com

 

[MHadden]

Thanks - Sorry I took so long to respond, my computer has been down for a while.
Yes, I do have one backend on the server & a copy of the FE on each user's computer. All computers have Access 2k installed on their computers also.
I was unaware about the issue of sharing the folder that contains the BE - I will definitely check into this. If you have any other ideas or input, I would greatly appreciate any guidance.
Thanks,
Michael
MHadden@knology.net
If you give someone a fish, you have given them a meal. If you teach someone to fish, you have given them MANY meals!

 

[MHadden]

Thanks again, but this didn't fix the problem. I have made sure that all mdb's are set to open shared & no one has permissions to open exclusive. I'm kinda at a loss, don't know where to turn. Any ideas would be greatly appreciated, but thanks for all input!
- Michael MHadden@knology.net
If you give someone a fish, you have given them a meal. If you teach someone to fish, you have given them MANY meals!

 

[MHadden]

Sorry, but I meant to say that I tried your suggestion as well as setting the above mentioned permissions.
- Michael MHadden@knology.net
If you give someone a fish, you have given them a meal. If you teach someone to fish, you have given them MANY meals!

 

[epoirier]

Really strange problem ! I never see that but i can't suggest to remove all your linking table, set to open "shared" to all your db on back/end and front/end in the option (repair and compile) and rebuilt your linking table. Me i working with A97 i set front/end to open eclusif and all back and to shared.

 

[thornmastr]

This is an interesting idea. Since he has a front end on every user’s computer, it should not make a difference; but it does bring something important to mind. If you open a database shared even if you are the only user, you will still get an ldb file simply because it is opened shared.

One thing he might want to check is if both people get an ldb file. More importantly, he should check for an ldb file when Access is not running on that machine. If he finds one, he has found his problem. It should not exist if Access is not running. Delete it, and that should solve his problem.
Robert Berman
Data Base consultant
Vulcan Software Services
thornmastr@yahoo.com

 

[MHadden]

Thanks, I'll give it a try & let everyone know
- Michael MHadden@knology.net
If you give someone a fish, you have given them a meal. If you teach someone to fish, you have given them MANY meals!

 

[Zeroanarchy]

Check the following.
1. the frontend file attribute is not set to read only on any of the systems

2. Check to make sure that your default open mode is set to "shared".
To do this goto Tools --> Options --> Advanced.

3. check to make sure that the default record locking is set to "No Locks"

4. Check with your server Administrator to make sure both users have the same user level if so it sounds like you have two copies of a front end on two diffrent machines, if not then you may find that the user is restricted in what they can do on the network.

5. Check the main form that all users enter into to make sure it is set to share and not one user at a time.

6. the only other thing is to be a bit more specific as to where the second user gets to before the program stops ie. does the user get to the password stage / does the program come up with an error on open.....

Let us know how you go.

ZeroAnarchy