Exclusive access not allowing changes.

[tom]

I tried to make change in one of my access forms
but the program wont let me because I dont have
exclusive access.

How to get exclusive access?

 

[Douglas J. Steele]

If you're running into that problem, it implies that you haven't split your
application into a front-end (containing of the queries, forms, reports,
macros and modules), linked to a back-end (containing the tables and
relationships). Only the back-end should be on the server: each user should
have his/her own copy of the front-end, preferably on his/her hard drive.

When you do that, then you can make changes to your heart's content without
any problems. Once you're happy that the changes are correct, give each user
a new copy of the front-end. (Tony Toews has a free Auto FE Updater
available at http://www.granite.ab.ca/access/autofe.htm to help in this
regard)

 

[tom]

If you're running into that problem, it implies that you haven't split
your application into a front-end (containing of the queries, forms,
reports, macros and modules), linked to a back-end (containing the tables
and relationships). Only the back-end should be on the server: each user
should have his/her own copy of the front-end, preferably on his/her hard
drive.

When you do that, then you can make changes to your heart's content
without any problems. Once you're happy that the changes are correct, give
each user a new copy of the front-end. (Tony Toews has a free Auto FE
Updater available at http://www.granite.ab.ca/access/autofe.htm to help in
this regard)

That is not the problem here. I am pretty certain anyway.
This was designed to be a front end. There is a back end
that the data in this database is linked to.

Perhaps it is the problem in some weird way if it implies
thus, but then how to find what is causing that?

 

[Douglas J. Steele]

That is not the problem here. I am pretty certain anyway.
This was designed to be a front end. There is a back end
that the data in this database is linked to.

Perhaps it is the problem in some weird way if it implies
thus, but then how to find what is causing that?

Where is the MDB file that you've got opened: on the server or on your
desktop? (If you're not sure, go to the Immediate Window using Ctrl-G, type
?CurrentDb.Name hit Enter and see what you get. If that raises an error, try
CodeProject.Name)

 

[tom]

Where is the MDB file that you've got opened: on the server or on your
desktop? (If you're not sure, go to the Immediate Window using Ctrl-G,
type ?CurrentDb.Name hit Enter and see what you get. If that raises an
error, try CodeProject.Name)

?currentdb.Name
C:\Documents and Settings\All Users\Documents\Sales.mdb

 

[Douglas J. Steele]

?currentdb.Name
C:\Documents and Settings\All Users\Documents\Sales.mdb

Unless your All Users folder is shared, I'd have to agree that the
implication is that you should have it opened exclusively.

When you shut down the application, does the locking file (Sales.LDB in the
same folder) go away? If not, try rebooting your machine: there may have
been an instance where the session didn't end properly. If after that,
you've still got the locking file, see whether you can delete it.

 

[tom]

Unless your All Users folder is shared, I'd have to agree that the
implication is that you should have it opened exclusively.

When you shut down the application, does the locking file (Sales.LDB in
the same folder) go away? If not, try rebooting your machine: there may
have been an instance where the session didn't end properly. If after
that, you've still got the locking file, see whether you can delete it.

It is in a shared folder. I copied it over to a folder
that is not shared and no more problem. I am still
not clear on why this happened.

 

[Guest]

If I download this free Auto FE Updater and everything works well. What
happens when another user creates a form or report in their front end copy
and they want the rest of the users to have that form or report as well. How
would she go about sending it to everyone? Would she also have to download
the Auto FE Updater? Would there be problems if we're both sending updates?

 

[Pat Hartman \(MVP\)]

In an environment where you will have multiple developers working with an
access application, you need to use a source control tool such as
SourceSafe. Each user checks out an object he wants to work on and checks
it back in when he's done.

Any other methodology is fraught with danger. It is extremely difficult to
keep a database in sync when multiple people have the ability to
add/change/delete objects.

Tony's Auto FE updater is intended to be used by the developers when they
want to distribute the finished database front end to each user's PC. It
will not work for your purpose.

 

[Tony Toews [MVP]]

If I download this free Auto FE Updater and everything works well. What
happens when another user creates a form or report in their front end copy
and they want the rest of the users to have that form or report as well. How
would she go about sending it to everyone? Would she also have to download
the Auto FE Updater? Would there be problems if we're both sending updates?

I would suggest you give your users an MDE containing all your
queries, forms, reports and VBA modules. An MDE means they can't
change the forms, reports or VBA modules. You *MUST* keep the MDB so
you can continue to make changes and make another MDE to give to the
users.

Then give the users another MDB which is linked to all the tables in
the backend. Don't use the Auto FE Updater to update this one. Let
them muck in there all they want creating queries, forms or reports.

If they have something they feel useful to you then they give that MDB
to you, you merge the appropriate objects into your master MDB, make
the MDE and distribute the new MDE.

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/