Distributing fixes/updates

[Guest]

I am in the process of developing an Access database which I am planning to package and distribute to customers using the packaging wizard

Once the users have entered data into the installed database, what is the best way for me to pass them updates/fixes without them having to run the complete repackaged installation again therfore overwriting the existing data

Can this be done using the replication or is there a better way

I was planning on distributing the databse as an .md

Any pointers would be appreciated

Many thanks

 

[Cheryl Fischer]

The best way to deliver updates of your application to clients without
jeopardizing their data is to distribute your application in TWO databases:
a Front-End (containing all Queries, Forms, Reports, Macros and Modules) and
a Back-End containing shared data tables. The vast majority of your updates
will likely be to the Front-End, so you can deliver a new copy of the MDB or
MDE to the clients safely and simply instruct them to copy it to the
location where the current Front-End is located.

Here is a link which you may find helpful:

How to manually split a Microsoft Access database:
http://support.microsoft.com/default.aspx?scid=kb;en-us;304932

There is also a Database Splitter utility included in most versions of MS
Access.

--

Cheryl Fischer, MVP Microsoft Access
Law/Sys Associates, Houston, TX

I am in the process of developing an Access database which I am planning

to package and distribute to customers using the packaging wizard.

Once the users have entered data into the installed database, what is the

best way for me to pass them updates/fixes without them having to run the
complete repackaged installation again therfore overwriting the existing
data.

 

[Guest]

Many thanks for that, looks exactly what I am looking for!