Maintaining live access installation

B

Bobk

What is the best way to update a live Access installation? I installed Access
in a shop floor environment where data is being gathered in real time. A
substantial amount of data has been gathered and is being used daily. I now
want to add more forms, queries and reports, but don't want to lose the
existing data. What is the best way to accomplish this?
 
D

Douglas J Steele

The application should be split into a front-end (containing the queries,
forms, reports, macros and modules), linked to a back-end (containing the
tables).

Assuming this is a shared database, only the back-end should exist on the
server: each user should have his/her own copy of the front-end, preferably
on their hard drive.

Even if it's a single-user application, it should still be split, since then
you can change the functionality of the application at any time, without
impacting the data.
 
B

Bobk

Thanks for the help.

Douglas J Steele said:
The application should be split into a front-end (containing the queries,
forms, reports, macros and modules), linked to a back-end (containing the
tables).

Assuming this is a shared database, only the back-end should exist on the
server: each user should have his/her own copy of the front-end, preferably
on their hard drive.

Even if it's a single-user application, it should still be split, since then
you can change the functionality of the application at any time, without
impacting the data.
 
L

lingram

You should create a two-tier solution. Create a new empty database (front
end) and import everything but the tables from your existing one. Then use
linked table manager to link to the tables in the original .mdb file. Then
you can replace the front end with new versions at will. You will only need
to change the back end when changes /additions to tables are necessary. The
original file (now the badk end) should eventually have all the
forms/queries/modules cleaned out. Use'rs should open the front end of the
database not the back end.
 
Top