By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,827 Members | 2,195 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,827 IT Pros & Developers. It's quick & easy.

Access 2002 exclusive mode -- not desirable

P: n/a
We just converted several of our major front-ends from Access 97 to
Access 2002. However there is an undesirable feature that we hadn't
anticipated in testing: the fact that changes to modules/forms/reports
cannot be saved since out applications are shared; that is, when
multiple users are in the application, we cannot change to exclusive
mode to save the changes since this would stop the work flow. This was
NOT a problem with Access 97! Is there a way to override this feature
in Access 2002?

TIA

gms--

Nov 12 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
"Greg M. Silverman" <gm*******@REMOVEMEumn.edu> wrote in message
news:bj**********@lenny.tc.umn.edu...
We just converted several of our major front-ends from Access 97 to
Access 2002. However there is an undesirable feature that we hadn't
anticipated in testing: the fact that changes to modules/forms/reports
cannot be saved since out applications are shared; that is, when
multiple users are in the application, we cannot change to exclusive
mode to save the changes since this would stop the work flow. This was
NOT a problem with Access 97! Is there a way to override this feature
in Access 2002?


Only to convert back to A97 :-)

Basically MS took the (not unreasonable) position that making design changes while
others were in the file was a bad idea anyway. But this was not just a "rule" that
was inserted. In A97 database objects were each stored as BLOBS in the system table
so they could be saved independently. In A2K and above the entire project is stored
in one big BLOB field so individual objects can no longer be saved. Every save saves
the entire project.
Nov 12 '05 #2

P: n/a
"Greg M. Silverman" <gm*******@REMOVEMEumn.edu> wrote:
We just converted several of our major front-ends from Access 97 to
Access 2002. However there is an undesirable feature that we hadn't
anticipated in testing: the fact that changes to modules/forms/reports
cannot be saved since out applications are shared; that is, when
multiple users are in the application, we cannot change to exclusive
mode to save the changes since this would stop the work flow. This was
NOT a problem with Access 97! Is there a way to override this feature
in Access 2002?


Don't your users have thier own copies of the FE MDB/MDEs? Or are you talking about
when doing programming?

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
Nov 12 '05 #3

P: n/a
Tony Toews wrote:
"Greg M. Silverman" <gm*******@REMOVEMEumn.edu> wrote:
We just converted several of our major front-ends from Access 97 to
Access 2002. However there is an undesirable feature that we hadn't
anticipated in testing: the fact that changes to modules/forms/reports
cannot be saved since out applications are shared; that is, when
multiple users are in the application, we cannot change to exclusive
mode to save the changes since this would stop the work flow. This was
NOT a problem with Access 97! Is there a way to override this feature
in Access 2002?


Don't your users have thier own copies of the FE MDB/MDEs? Or are you talking about
when doing programming?


Users were sharing the Access file (developers had their own copy)... we
are in the process of going to the distributed MDE model, so this will
all be moot.

Thanks!
gms--

Nov 12 '05 #4

P: n/a
"Greg M. Silverman" <gm*******@REMOVEMEumn.edu> wrote:
Users were sharing the Access file (developers had their own copy)... we
are in the process of going to the distributed MDE model, so this will
all be moot.


Good. FWIW I specifically created the Auto FE Updater utility so that I could make
changes to the FE MDE as often as I wanted and be quite confident that the next time
someone went to run the app that it would pull in the latest version. For more info
on the errors or the utillity see the free Auto FE Updater utility at
http://www.granite.ab.ca/access/autofe.htm at my website to keep the FE on each PC up
to date.

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
Nov 12 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.