Working on a DB while client is using it?

[MediaDoc]

Newbie question here.

Client and I are in different cities. Whenever they want modifications to their database, I ask them to compact / repair it, email it to me (its ~ 3MB), and then I work on the new reports, tables, logic etc... then send it back. Leaves them without a DB for a couple days - week.

Is there a better way to do this? Ideally I could send them all the underlying structure stuff, that they could import into thier database.

(I have used the import queries / reports function - but it is rather tedious for the end user to do, esp. when lots of things change).

Regards,

Matts

 

[DBL]

If It's the frontend you are working on rather than the data, you should split the database into frontend/backend, there is a wizard for doing that. Then, you can work on the frontend (forms, queries, reports, etc) without disturbing them and email the new frontend to them when it's ready (while they work away using the old version in the meantime). They just overwrite their existing frontend with the new one and that should be it.

If it's the backend that you are working on the only way I can think if accessing it using PC Anywhere or something like that.

 

[ElsVanMiert]

Here is an article from the ACCESS ONLINE ENCYCLOPEDIA at www.unsoftwareag.com concerning Frontend/Backend architecture

Article Code: G9

How do I split my application in frontend and backend?
PROBLEM


If all database objects (tables, queries, forms, reports, macros and modules) are located in one single (MDB) file then you have (at least) two problems:
1. a direct update of your non-table-objects will overwrite the table data
2. You can not use your application in a multi-user environment.


Solution

Simply follow these steps:
Copy your MDB
Open the copy
Delete all database objects EXECPT the tables
Close and compact the copy
Rename the copy "Backend.MDB" br> Open the original
Close all tables
Link all tables from the Backend.MDB into this MDB
Close and compact this file
Rename this file "frontend.mdb"

Notes

From now on you can update the non-table-data in just replacing the frontend MDB with a new version. The data of the backend will remain unchanged.
Modifications of the table structure of the backend require SQL-DLL or ADO/DAO programming.
If you move or rename the backend file then you need to relink the linked tables.
If you move the backend on a network server multiple frontend files on the clients can access the same data.