You do not have exclusive access

[millwheal]

I have an Access 2003 database residing on a server and used by multiple users. The only security is that a password is required to open the file.

It is common practice for some of the users to create one-off reports, etc. to meet ad hoc information requirements. Until recently, the database was Access 97 format, and users were able to carry out their activities as needed.

Since the database was converted to Access 2003, no-one can create or amend reports. The warning message "You do not have exclusive access to the database at this time..." appears, and if they proceed, they are always subsequently told that the new or amended object cannot be saved. This situation occurs even if the user attempting the change is the only user of the database at the time.

Curiously, I have another Access 2003 database on a server which does not give this problem. This database is not password-protected and I am [almost always] the only user. Other people could use the database; it just so happens that they do not usually do so.

I have compared various option settings, etc. on the two databases, and the only difference I can see is that one has a password at startup and one doesn't.

Any suggestions would be welcome!

millwheal

 

[James Dudden]

Hi,
The problem is an Access 2003 "upgrade". You can not make changes to the database whilst someone else is logged in. If you want to be able to make design changes to forms and reports you need exclusive access. This is why your other database works - you are the only user.

Regards
JD

 

[millwheal]

Hi James,

Thanks for that info, but I'm not sure that is the problem. As I said in my original posting, the normally multi-user database prevents changes even when there is only one user active.

millwheal

 

[KathyL]

Get used to it. Access 2003 requires you to have exclusive access to modify. Set yourself up to have a development partition, and a production partition. Anyone making design changes should work in the development partition. You’ll have to export changes over to the production partition, but only when you again have exclusive access.

Try doing a compact and repair. If all else fails, you may have to export everything to a new blank database.

Wait until you get to 2007, you’ll have another challenge with it’s trusted environment requirements!

 

[millwheal]

Another MS improvement!
I surrender and will have to find some other way around the problem.