Error: You do not have exclusive access to the database

[shades234]

When i go to open my Access database from certain computers, i get multiple popup messages stating the same thing. They all say "You do not have exclusive access to the database at this time. If you proceed to make changes, you may not be able to save them later [Show Help >>] [OK] [Cancel]"

Now, when I open the db from different computers, I don't get the error on open, but if I try to open a form in Design Mode.

There is a program running that has "control" over the database. All this program does create new records in the main table, and creates a "data" table for the new record entered in the main table.

Is there a setting that Access has to open the most recent form or anything in design mode? Can that be changed? Has anyone ever encountered this error?

I thank you in advance for your time to look over my problem.

Thanks

[NeoPa]

This message comes up when the database is open anywhere (It can even be in a separate Access session on your own PC.) and an object is open in design view. It applies to forms; reports; some others but not to Tables & Queries I think.

[shades234]

Thanks NeoPa.

Is there any way to disable objects from opening in design mode on access/db startup?

[NeoPa]

:confused:
I don't think that any objects will open automatically to design view on open.
The area to look at for automatically opening objects or running code is Tools / Startup... though.

[shades234]

OK. That's kinda funny.

On my 3 different computers, the file opens fine. When i try to go to design mode, then i get a problem.

However, one user on a laptop wants to open in the design mode. I tried 2 other users for the laptop, and no problem. I find it unusual that onlly one user wants to "open in design mode"

I'll try and look more into it.

[NeoPa]

Do they understand what Design Mode is?

[shades234]

Do they understand what Design Mode is?

yes, because i'm the one opening everything. I'm testing a db that will be used by different people.

[NeoPa]

I'm not sure that explains why they would have to know about design mode. Clearly you do, but they (users) would not generally be expected to go within a mile of design mode in a database.

[shades234]

I'm not sure that explains why they would have to know about design mode. Clearly you do, but they (users) would not generally be expected to go within a mile of design mode in a database.

yeah, sorry. i wrote that reply in the midst of doing other work. i thought i had more, obviously not.

yes, i know about design mode. yes, the users of the db will not need to know, nor should they ever go near, the design mode.

now, let me restate again what is going on. there is a program (hidden) that runs in the background of the "db server" i.e. the computer where the db is located. it basically has the db open, so data can be entered to the db. now the users can open the db via network connections to view different reports and forms based off of this information. while testing the db, i was able to open the db on several computers. i wasn't able to make any code/apperance changes to the db (due to the hidden program).

when i would go to design mode from my computer, (while the hidden program was running) i would get an error saying changes would'nt be saved. howeveer the db would open fine (no errors about saving issue). this was the cse in two other computers. however, when opening the db from one of our laptops, the no save error would come op on the db open, thus making the "user" click ok about 8 times (for the different forms/reports that might be changed)

my only guess is that on the laptop, the db seems to open in design mode. i was trying to figure out what settings may cause this.

[MMcCarthy]

Standard practice is that you wouldn't open a form from an operational database in design mode. This should always be done on a copy of the database which can then be uploaded as the operational database. You don't say if the database has a front and backend. This is one of the reasons why it is necessary. It means you can upload a new frontend without disturbing the data.

Mary

yeah, sorry. i wrote that reply in the midst of doing other work. i thought i had more, obviously not.

yes, i know about design mode. yes, the users of the db will not need to know, nor should they ever go near, the design mode.

now, let me restate again what is going on. there is a program (hidden) that runs in the background of the "db server" i.e. the computer where the db is located. it basically has the db open, so data can be entered to the db. now the users can open the db via network connections to view different reports and forms based off of this information. while testing the db, i was able to open the db on several computers. i wasn't able to make any code/apperance changes to the db (due to the hidden program).

when i would go to design mode from my computer, (while the hidden program was running) i would get an error saying changes would'nt be saved. howeveer the db would open fine (no errors about saving issue). this was the cse in two other computers. however, when opening the db from one of our laptops, the no save error would come op on the db open, thus making the "user" click ok about 8 times (for the different forms/reports that might be changed)

my only guess is that on the laptop, the db seems to open in design mode. i was trying to figure out what settings may cause this.