Exclusive Access

[millwheal]

I have an Access 2003 monolithic database on a server, being accessed by a number of users, running Windows XP SP3. Since very few of the users make 'structural' changes, the lack of "Exclusive Access" is not usually a problem, and I only make changes when everyone else is logged out at the end of a day.

Recently, we have noticed an apparent anomaly. If anyone tries to create a new Report, or amend an existing one, the "you do not have exclusive access ..." message instantly appears and the new or amended report cannot subsequently be saved.

However, new Tables and Queries can be created and saved, and existing Tables and Queries can be amended and saved.

Is this by design, a "known fault", or what?

Any help would be much appreciated.

 

[boblarson]

1. If this database is not split (backend with tables and a copy of the frontend on each user's computer, you are playing Russian Roulette with corruption.

2. If a user is in the database and a network disruption occurs, no matter how slight, you can probably kiss your database goodbye and will have to restore from a backup copy and then re-enter any data that was done after the backup.

3. Read this on why you should split.

4. You might be suffering from corruption as we speak, given your problem.

 

[gemma-the-husky]

I have an Access 2003 monolithic database on a server, being accessed by a number of users, running Windows XP SP3. Since very few of the users make 'structural' changes, the lack of "Exclusive Access" is not usually a problem, and I only make changes when everyone else is logged out at the end of a day.

Recently, we have noticed an apparent anomaly. If anyone tries to create a new Report, or amend an existing one, the "you do not have exclusive access ..." message instantly appears and the new or amended report cannot subsequently be saved.

However, new Tables and Queries can be created and saved, and existing Tables and Queries can be amended and saved.

Is this by design, a "known fault", or what?

Any help would be much appreciated.

if multiple users are sharing the same database - then you wont be able to change it, necessarily. If no-one actually has a given entity open, then you may be able to change that entity, so it's suck it and see, really.

However, the split database already alluded to is most important!

 

[CBrighton]

3. Read this on why you should split.

FYI this webpage seems to have been deleted.

 

[boblarson]

FYI this webpage seems to have been deleted.

Thanks, I'll have to check it out and see if he moved it.

 

[millwheal]

Bob,
I'd be very grateful if you could post a current link for the 'split database' file as I think that is what I am going to have to do.

 

[boblarson]

It isn't the same article but this should help.

http://support.microsoft.com/kb/304932

 

[millwheal]

Bob,
Thank you for that. It is useful, but somewhat long on the "how" [which I know] and short on the "why" [some of which I know, but would like to know if there is anything more]. If you are aware of anything else in this area, I would be grateful for a link.

 

[boblarson]

Okay, check this out:

http://www.techrepublic.com/blog/10things/10-reasons-to-split-an-access-database/1119

I disagree with item #11 to some extent (unless you use RDP, Terminal Services or Citrix), but the rest is good.

 

[millwheal]

Bob,
That's excellent; just what I needed. Thanks for all your help.