Exclusive rights in XP different from '97 version?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

TRob - 12 Jul 2005 17:10 GMT

I developed quite a few databases in Access ’97. The databases are on a LAN
and have multiple users. The user group has just recently been moved from NT
to XP. The conversion from 97 to XP went fine, but I’m having trouble with
maintenance.

For example, I received an error message that I need exclusive access to the
database in order to add a new macro. I’m not attempting to change an
existing macro, just add a new one.

This didn’t happen in the ’97 NT version of MSAccess. Is this something
that changed with the 2003 XP version of Access or is there a default setting
somewhere that is preventing me from doing this? Hopefully something I can
easily change??

Ultimately, I would like to be able to make changes behind the scenes while
others are in the database.

Thanks

Reply to this Message

Joan Wild - 12 Jul 2005 23:59 GMT

>I developed quite a few databases in Access '97. The databases are on a
>LAN
[quoted text clipped - 19 lines]
> while
> others are in the database.

You have made references to moving from NT to XP (implies an upgrade to the
Operating System which has nothing to do with Access).

But then you make reference to Access 97 being upgraded to 2003 XP. there
is an Access 97, Access XP (also known as 2002), and there is an Access
2003.

Taking a guess here that you upgraded to version 2003 on Windows XP.

Starting with Access version 2000, one needs exclusive access to a database
in order to make design changes.

You should split your database, as having multiple users use the same mdb
file will likely lead to corruption. Also by splitting, it allows you as
developer to work on frontend objects exclusively, as no one else will be
using your frontend. Once you have things to your liking you redistribute
the updated frontend to your users. Tony Toews has a tool to aid in
updating the frontends. See www.granite.ab.ca/autofe.html

To split means that you have two mdb files. The backend (just the
tables/relationships) sits on the server. The frontend (containing all
other objects, and linked tables - linked to the backend) sits on each
user's computer.

Signature

Joan Wild
Microsoft Access MVP

Reply to this Message

Van T. Dinh - 13 Jul 2005 01:47 GMT

Agree 100% with what Joan wrote and only small correction to the link:

http://www.granite.ab.ca/access/autofe.htm

Signature

HTH
Van T. Dinh
MVP (Access)

> You have made references to moving from NT to XP (implies an upgrade to
> the Operating System which has nothing to do with Access).
[quoted text clipped - 19 lines]
> other objects, and linked tables - linked to the backend) sits on each
> user's computer.

Reply to this Message

TRob - 13 Jul 2005 17:19 GMT

Thanks for the info. I already have a front end and back end, but both are
on our LAN, so I suppose my "front end" is not a true front end at all since
it is shared by multiple users as well.

Thanks!

-----------------------------------------

> Agree 100% with what Joan wrote and only small correction to the link:
>
[quoted text clipped - 23 lines]
> > other objects, and linked tables - linked to the backend) sits on each
> > user's computer.

Reply to this Message

Joan Wild - 13 Jul 2005 20:37 GMT

> Agree 100% with what Joan wrote and only small correction to the link:
>
> http://www.granite.ab.ca/access/autofe.htm

Thanks Van. I was going from memory as I was offline.

Signature

Joan Wild
Microsoft Access MVP

Reply to this Message