Version updates

[Ardus Petus]

I have a customer who uses a .mdb database I wrote.
How should I structure my project so that (code and structure) updates can
take place without changing my client's data?

TIA

 

[Douglas J. Steele]

The standard approach is to split your application into a front-end
(containing the queries, forms, reports, macros and modules), linked to a
back-end (containing the tables and relationships). Only the back-end is
placed on the server: each user has his/her own copy of the front-end,
preferably on his/her hard drive.

For more information about splitting, see what Tony Toews has at
http://www.granite.ab.ca/access/splitapp/index.htm. While you're there, make
sure you check out the free Auto FE Updater he has at
http://www.granite.ab.ca/access/autofe.htm so that you can ensure that each
user has the most up-to-date version of the front-end.

 

[Ardus Petus]

How do you re-establish links to linked tables?

The standard approach is to split your application into a front-end
(containing the queries, forms, reports, macros and modules), linked to a
back-end (containing the tables and relationships). Only the back-end is
placed on the server: each user has his/her own copy of the front-end,
preferably on his/her hard drive.

For more information about splitting, see what Tony Toews has at
http://www.granite.ab.ca/access/splitapp/index.htm. While you're there,
make sure you check out the free Auto FE Updater he has at
http://www.granite.ab.ca/access/autofe.htm so that you can ensure that
each user has the most up-to-date version of the front-end.

 

[Douglas J. Steele]

See http://www.mvps.org/access/tables/tbl0009.htm at "The Access Web" for a
good approach.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

How do you re-establish links to linked tables?

 

[Ardus Petus]

Sorry for very late thanks!

--
AP

See http://www.mvps.org/access/tables/tbl0009.htm at "The Access Web" for
a good approach.