How to update DB in use..

[Yitzak]

Hi

I have a CustomersDB.mdb which I need to update and have written quite
a long upgrade module in VBA to add fields, relationships, change
data etc etc.

There is another DB call it Sales.mdb that is used heavily, there is a
linked table in Sales.mdb pointing to the actual tblcustomers in
customers.mdb.

Is there a way to make this Read-only from the Sales.mdb.

My real issue I can take a copy of CustomersDB.mdb tell its users not
to make changes just read while I'm updating then run my VBA routines
and itegrity checks. Once I'm happy with it.

I'll copy my amended copy back over the original, problem the users of
Sales.mdb will need to come out, is this the case? Am I risking
corrupting the DBs with this approach.

[Tom van Stiphout]

Re: How to update DB in use..

On Thu, 21 Feb 2008 15:47:51 -0800 (PST), Yitzak
<terryshamir@ya hoo.co.ukwrote:

Don't do this work while users are in the DB. That's asking for
trouble. You can't even make a reliable backup when users are in the
DB. Do this after hours.

-Tom.

>Hi
>
>I have a CustomersDB.mdb which I need to update and have written quite
>a long upgrade module in VBA to add fields, relationships, change
>data etc etc.
>
>There is another DB call it Sales.mdb that is used heavily, there is a
>linked table in Sales.mdb pointing to the actual tblcustomers in
>customers.md b.
>
>Is there a way to make this Read-only from the Sales.mdb.
>
>My real issue I can take a copy of CustomersDB.mdb tell its users not
>to make changes just read while I'm updating then run my VBA routines
>and itegrity checks. Once I'm happy with it.
>
>I'll copy my amended copy back over the original, problem the users of
>Sales.mdb will need to come out, is this the case? Am I risking
>corrupting the DBs with this approach.
>
>