Hello.
I have inherited a database where I work which lives on a shared drive and
have been given the chjallenge of making modifications to various tables
(structure & data) & VB code. The question I have is fairly basic. What is
the best way to update the code, etc. for a shared Access database on a
network drive so there is minimal -no downtime for the users. I do the
"development" on my machine, but the database on the shared drive is used by
multiple users.
> Hello.
>
[quoted text clipped - 7 lines]
> by
> multiple users.
You should split the database into frontend/backend (frontend contains all
objects except tables, and is linked to the backend which contains only the
tables). Make the changes you need in the frontend and deploy to users once
you've completed testing.
Tony Toews has a tool to assist with deploying frontends. See
www.granite.ab.ca/autofe.html
For any changes to the backend (which really shouldn't be that often if
you've done your planning), you'll need to get everyone out while you make
the changes.

Signature
Joan Wild
Microsoft Access MVP
Pamela - 12 Aug 2005 20:03 GMT
Thanks for your explanation. I apologize for the delayed response. They
want me to do this on multiple front-ends, on various shares...
>> Hello.
>>
[quoted text clipped - 13 lines]
>you've done your planning), you'll need to get everyone out while you make
>the changes.