ACCESS - Workgroup file - pc lockup, file lock

[michmcgrath]

The format is 2000, created using 2002, it is still in development.
There is a workgroup file that determines permissions, users login
The workgroup and database are located on a network where users gain access to the database through one shortcut that runs the database using the same workgroup file. (this appears to work fine, users login) This is in place to keep users from gaining access to forms, reports and certain features.

I have had 3 people in it at the same time in the past as a test, they were all running Office 2003, and there did not seem to be any file sharing/locking issues. A group of us (5 people) recently went to use the database in a training room with computers running Office 2007. The database was locking up on individual computers, and messages appeared on a couple of the computers saying "file is locked" or something of that nature.

I do NOT want to split the database (because of maintenance) and I believe there must be a way to have multiple users using the same database, forms etc.

Any suggestions are appreciated.

Also, would making MDE file help at all?

Thank you very much!

[ADezii]

Before we go any further, check the following:

1. Office Button
2. Access Options
3. Advanced Option
4. Advanced Section
5. Make sure Default open mode is set to Shared and NOT Exclusive

[michmcgrath]

Thanks for the response. Yes it is set to shared. It is setup on a network, there is a workgroup file with several users. I have logged in as other users, the logins work and permissions work. THis is new database, a few of us have had it open testing it out using Office 2003, but recently as I mentioned we opened it using the same shortcut and workgroup file, with Office 2007 and thats when problems started.

I have read about splitting and how that resolves issues, but I do not want to do that. I need to move in the direction of Office 2007, since we are upgrading (no choice) to that version. I understand that version will allow workgroup files from prior versions, but does not allow for creation of workgroups?

I want to be able to share the database on a network, with approx 10 users and have it function like it should. Having the ability to permit accessibility to specific forms is a plus. This is my goal, but since I am moving to 2007, I guess I should be looking at doing this in 2007.

Thanks again.

[ADezii]

Thanks for the response. Yes it is set to shared. It is setup on a network, there is a workgroup file with several users. I have logged in as other users, the logins work and permissions work. THis is new database, a few of us have had it open testing it out using Office 2003, but recently as I mentioned we opened it using the same shortcut and workgroup file, with Office 2007 and thats when problems started.

I have read about splitting and how that resolves issues, but I do not want to do that. I need to move in the direction of Office 2007, since we are upgrading (no choice) to that version. I understand that version will allow workgroup files from prior versions, but does not allow for creation of workgroups?

I want to be able to share the database on a network, with approx 10 users and have it function like it should. Having the ability to permit accessibility to specific forms is a plus. This is my goal, but since I am moving to 2007, I guess I should be looking at doing this in 2007.

Thanks again.

I understand that version will allow workgroup files from prior versions, but does not allow for creation of workgroups?

To the best of my knowledge, the Workgroup concept has been dropped from Access 2007, it exists solely for backward compatibility.

Just as an experiment, and if you are not using Access 2007 specific features such as Attachments, and Multivalued Fields, you can try saving the Database in the Access 2002/2003 Format, and see what happens. I know that this is a long shot, but it may be worth a try.

P.S. - Another shot in the dark while I'm thinking. Try having the Workgroup Information File reside locally on each PC, as opposed to being on the Server, with the Shortcut pointing to it, and see what happens.

[michmcgrath]

Thank you for the quick response. I broke down and split the database with the BE located on the network. Not what I wanted to do, but I ddi it to check performance etc.

It is extremely slow, it takes a long time to load forms that are attached to tables. Do you have any suggestions for improving this? I am still using 2003 at this point, but will be converting to 2007.

Thanks.

[michmcgrath]

I decided today to have 5 people login using Access 2002/2003. Before they did that, I changed the format of the database from 2000, to 2002/2003. All users were using MS Access 2003 to open the database. THey accessed the database through the same shortcut using the workgroup file that was originally created.

This appears to be the answer to the problem: the format of the database versus the version of the program used. Once the format of the database was changed to correspond with the version of the software used, the errors and lockups disappeared.

Do you have any thoughts on this? Do you believe this could be the problem, and do you think that the database will remain consistent in the way it functions?

I also changed the queries that the forms were bound to, to "no locks". I do not think this was the problem, but I can not be sure.

I plan to have another testing day sometime soon. If that works then we can begin logging data using 2003. I will however, copy the database and begin converting to 2007 so that we are prepared when the day arrives that we are forced to use 2007.

THanks again for the suggestions.

[michmcgrath]

PS: I forgot to mention that I went back to my original version of the database, it is NOT SPLIT.

[paulw1]

I can't help. other than to say that I have just come across the same problem with two Access databases in the same folder, 1 is an .mdb file, the other in the 2007 format.

The only thing I can identify is that the locking issue appears to be with users who have "read only" rights to the folder. Those with full ownership seem to be ok.

Does this throw any light on the problem?