• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 244
  • Last Modified:

Only one person can open an access database at a time

Help,  only one person can open an access database at a time.  I believe it was created with office 2000 or 2003 but I'm not sure.  Users using Office 2003 can only open it one at a time but two users with office 2007 beta version can open it anytime someone else has it open.  It's default is set to open in shared mode and everyone has full control of the database in the security properties.  This just started happening.  Could it have something to do with office 2007 beta version.  The person who opened it with that said they didn't convert the database.

Ok now I've narrowed down the problem to the fact that people who have access 2000 or 2007 can open any database while other users have it open no matter which version of access has it open but the users who have access 2003 can only open it if no one else has it open.  Even if it is a user who originally opened it with access 2003 the second access 2003 user cannot open it.
0
Steelin_It
Asked:
Steelin_It
  • 5
  • 3
  • 3
  • +1
1 Solution
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
Typically this is due to either (a) someone opening the database in Exclusive mode or (b) one or more users do NOT have the proper Windows permissions on the folder housing your database.
0
 
Steelin_ItAuthor Commented:
Everyone has full control of the folder and the database.  I just discovered that a person with an older version of Access 2003 w/sp2 can open it when other people have it open.  I just recently purchased an oem version of office 2003 a week ago so it's newer than the other office 2003 installation.  The machines with that installed on it are the only ones that have this problem.  Could that be a problem?  Could it be an office update the other older access 2003 machine doesn't have?  The new machines have all of the office updates installed on them but the older machine with 2003 probably only has office 2003 sp2, not any other updates.
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
How are they opening the database? Do they all have shortcuts that "point" to the database? Does each user have their own copy of the frontend, which are all connected to the same backend?
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
Steelin_ItAuthor Commented:
I'm not a big access guy, mostly networking.  But they all use shortcuts to get to it but I tried opening the database directly as well.  Sorry I don't know what front-end/back-end means.  I'm guessing it means everyone opens their own copy of the database and then writes to it and saves it to a master copy but that's not how they do it.  The database is on a windows 2000 server that everyone has access to.  Each person opens the same database from the same location on the network.  This just started happening with the new computers running MS XP Pro sp2 with a recently purchased install of Office 2003 sp2.  But like I said before a pc running win xp pro sp2 with an older version of office 2003 sp2, and possibly without all of the MS updates does not have this problem.
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
The "frontend" is an Access database (or VB program, or ASP page) which contains the user interface items - forms, reports, etc. The "backend' is the actual datafiles (the tables, in other words). EAch user should have their own copy of the frontend, and they should all connect to the backend.

Have all users log out and see if you find an errant Locking file in the folder on Windows 2000 server where the db lives ... the Locking file will be named the same as the Access database but will have an .ldb extension - for eg, if I have a database named MyStuff.mdb, the lockfile will be named MyStuff.ldb. Delete this file and see if it fixes your troubles.

The Lock file stores information about the connected users, the records they're viewing, etc. It's created by the first person to open the database, and then as each other person adds to the database they update this lockfile. When the last person exits the db, the lockfile is destroyed and the cycle begins again.

Doublecheck the Windows permissions on the folder to make sure that all have the correct permissions on the folder on the Windows 2000 server. This is probably the biggest cause of the troubles you're seeing ...
0
 
harfangCommented:
Hello Steelin_It

At first, it would seem that your Access2003 versions insist upon opening the database in exclusive mode. However, you already took steps to ensure that they don't, and it's also infirmed by the fact that you can open the database with other versions even it is is open with Access2003 first. Can you confirm that?

So what remains is that Access2003, although not attempting an exclusive open, fails when the database is open. This could be caused for example by a timeout or some other obscure registry key settings.

Another potential problem is the cohabitation of different versions of Access. Are your Access2003 installed alone on their computer? Also, Access2007 could have set a flag when "enabling" the database that conflits with Access2003. This seems unlikely, though, but MS isn't above unlikely bugs. Should that be the case, the latest SP for Access2003 would probably solve it. (I'm really fishing here, I have no experience with Access2007 at all).

Finally, although I should have mentioned this first, you normally get an error message when something fails. What is that error message?

(°v°)
0
 
Steelin_ItAuthor Commented:
No errors and permissions are fine.  One thing I just thought of.  Even though these two machines came from Dell with liscensed os on them, I don't like how Dell partitioned the harddrives and insttalled all of their own extra software so I formatted one of the hard dirves and reinstalled the os and only the programs I wanted on there.  To make things faster on the next install I made a ghost image of the first machine and put that image on the second machine.  I changed the computer name of the second machine and then added it to the domain.  I thought maybe it was because they both had the same copy of office 2003 on them so I unistalled it on one of them and then reinstalled it from a different oem copy I have but still had the same problem.  I uninstalled that copy of 2003 and installed office 2000 thinking that that would solve my problem but it didn't.  I then looked at the system properties and noticed the the xp os on both computers were registered to the same person with the same serial number due to the fact that it's a ghost image.  Could that be the problem?  I can't think of anything else.
0
 
harfangCommented:
Same problem with all databases? What if you create a new one, is that shareable?
(°v°)
0
 
Steelin_ItAuthor Commented:
All databases.  Haven't tried a new one yet.  Let you know.
0
 
harfangCommented:
I must say I'm out of ideas. If two A2003 installations with the lates service packs and patches applied cannot share a database, and that without even an error message, I would just throw them out, I guess...
(°v°)
0
 
Steelin_ItAuthor Commented:
I ended up having to install a fresh os and then install office 2003 on it to get them to work.  What a pain.  Does anyone know if Symantec Norton Ghost is aware of problems like this?  I never used to have trouble with ghost images back in the day but with the way software licensing is today I wonder if Syamantec has a workaround for this.
0
 
DarthModCommented:
PAQed with points refunded (500)

DarthMod
Community Support Moderator
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 5
  • 3
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now