Suppress exclusive access message

I have a db that resides on a server and is shared from a number of different
locations. I have designed an updateable form based on a query that is not
updateable. This works just fine in a single user environment.
Unfortunately, when a change is made and another user is logged in, the
"exclusive use - may not save changes message" pops up. It appears that
the change is saved unless another user is in the same record. Is there any
way I can suppress this message - the users do not like it.
TIA
Bibi

Unless I'm missing something, supressing the message won't do a lot of good,
since "exclusive" use means whoever is #2 will not be able to make changes
(no matter what message they see or don't see). Instead, take a look into
why this message is happening.

It may be that the users don't have full read/write permissions on the
folder in which the db resides.

Regards

Jeff Boyce
Microsoft Office/Access MVP


"Bibi" wrote in message
...
I have a db that resides on a server and is shared from a number of
different
locations. I have designed an updateable form based on a query that is
not
updateable. This works just fine in a single user environment.
Unfortunately, when a change is made and another user is logged in, the
"exclusive use - may not save changes message" pops up. It appears that
the change is saved unless another user is in the same record. Is there
any
way I can suppress this message - the users do not like it.
TIA
Bibi

Bibi wrote:

I have a db that resides on a server and is shared from a number of different
locations. I have designed an updateable form based on a query that is not
updateable. This works just fine in a single user environment.
Unfortunately, when a change is made and another user is logged in, the
"exclusive use - may not save changes message" pops up. It appears that
the change is saved unless another user is in the same record. Is there any
way I can suppress this message - the users do not like it.


You want to split the MDB into a Front End MDB containing the queries,
forms, reports, macros and modules with just the tables and
relationships in the Back End MDB. The FE is copied to each network
users computer. The FE MDB is linked to the tables in the back end
MDB which resides on a server. You make updates to the FE MDB and
distribute them to the users, likely as an MDE.

See the "Splitting your app into a front end and back end Tips" page
at http://www.granite.ab.ca/access/splitapp/ for more info. See the
Auto FE Updater downloads page
http://www.granite.ab.ca/access/autofe.htm to make this relatively
painless.. The utility also supports Terminal Server/Citrix quite
nicely.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/