Database splitting (XP, 2000)

Topic

New Reply

I just developed my first Access database (for a relative) and realize that I need to split the database. Having read what I can about the subject in Access help, I find I still don’t fully understand the process.

Specifically, I will be the person who maintains (makes changes & enhancements) the database and I want to be able to work on the design here and email the database to them. As they fill it with data, it will become too large and impractical to email back and forth.

So, if I send them a split database and tell them how to successfully link the back end & front end, what is involved in applying new forms that I might create or old forms I might modify? They are not especially technical so I will need to talk them through it or provide “how to” documerntation.

Also, what if I need to modify a table structure or add a table? How does that get into their database without disturbing the existing data?

Sorry if this sounds like I am confused… obviously, I am.

Reply | Quote

Replies

If your contact with the client is via e-mail, updating the backend is going to be a problem, since you won’t be able to edit it directly. Once the client starts to fill it with data, it may soon become too large to send back and forth via e-mail. Perhaps the BackEnd Upgrader from DataBase Advisors can help (WMVP carbonnb is one of the developers of this free utility.)
The front end should be easier – unless the client creates or edits forms, reports etc. himself, you can just send a new version of the front end to replace the existing version.

Reply | Quote

If your contact with the client is via e-mail, updating the backend is going to be a problem, since you won’t be able to edit it directly. Once the client starts to fill it with data, it may soon become too large to send back and forth via e-mail. Perhaps the BackEnd Upgrader from DataBase Advisors can help (WMVP carbonnb is one of the developers of this free utility.)
The front end should be easier – unless the client creates or edits forms, reports etc. himself, you can just send a new version of the front end to replace the existing version.

Reply | Quote

You might also find our tutorial useful in laying out the process for splitting a database.

Reply | Quote

You might also find our tutorial useful in laying out the process for splitting a database.

Reply | Quote

Provided you don’t store anything in the frontend (configuration tables, etc.), you can just e-mail them the entire frontend whenever you make changes. They will have to relink to their backend. Make sure you compact/repair the database before you send it to keep in within a manageable size (if it starts getting too big, zip it first). Your frontend would have to get pretty large before this becomes impractical. You could also just send an “update” database that contains the frontend objects you are changing, then talk them through how to delete these objects in their database and import them from the update database.

Updating the backend is more difficult. You could use GoToMyPC, so you could actually directly work on their machine. You can also make most modifications via SQL (creating/modifying tables, fields, indexes, etc.), but that would take a little time to learn (then you could teach me).

Reply | Quote

Provided you don’t store anything in the frontend (configuration tables, etc.), you can just e-mail them the entire frontend whenever you make changes. They will have to relink to their backend. Make sure you compact/repair the database before you send it to keep in within a manageable size (if it starts getting too big, zip it first). Your frontend would have to get pretty large before this becomes impractical. You could also just send an “update” database that contains the frontend objects you are changing, then talk them through how to delete these objects in their database and import them from the update database.

Updating the backend is more difficult. You could use GoToMyPC, so you could actually directly work on their machine. You can also make most modifications via SQL (creating/modifying tables, fields, indexes, etc.), but that would take a little time to learn (then you could teach me).

Reply | Quote