On Apr 9, 1:53 pm, "OdieTurbo" <todd.quig...@gmail.comwrote:
Quote:
On Apr 9, 1:35 pm, kcop...@hotmail.com wrote:
In the past, I've seperated the database to a "Front End" and "Back
End" schema. Utilize the "Back End" (an Access Database) to house all
the data, while the "Front End" (another Access Database) points to
the back end to acquire the data.
>
This way, when you change the back end, you can update the front end
and copy it to their desktop without a loss of data. You can even
incorporate "version control" in which the front end will check the
version of the back end. This way the users can run a shortcut to
copy the newer version to their desktop.
>
I can provide some reference sites for implementing this.
>
OT
I'm sorry, your suggestion to split the database doesn't appear to
answer my question as to how to add a field to a database that is in
another remote location. Perhaps I wasn't very clear before: the 10
database copies are in remote office locations (different towns) that
are not networked, and each office only has dialup access to the
internet. I have a routine that works well for sending new versions of
forms, reports and queries by email (as they don't affect data), but
this time I need to update the table structure within each database
and I'm trying to save the hassle of having someone drive around for a
day visiting each of the 10 remote sites just to add a new field to
one of the tables. As I said before, it's not as simple as creating
one updated table and sending it out, as each of the 10 locations has
different data within their database that I do not want to distrub.
If you have reference sites on how to add a field to a table through
code or macro without distrubing the data already in the database,
that would be appreciated.
KC