Partially Disconnected Databases
- From: "campbell_canuck" <chenschel@xxxxxxxxxxx>
- Date: 25 Mar 2006 12:45:55 -0800
I'm hoping to get a little advice.
I currently have a repository db that is located on a server. There
are a number of client databases that have their own interfaces (forms,
reports, queries) but use the repository db for storing data.
There is a new requirement for some users to be able to upload limited
and specific information to a laptop (or tablet), take it into a remote
(ie disconnected) environment, and update the information. On
returning to the office (and connecting to the network, either wireless
or with a network cable), the users need to be able to update the
repository db with the information they have entered in the remote
I've been instructed that Access is what the application MUST use.
So this is what I'm thinking of doing:
Each laptop would have a small db of its own. This would contain the
information the user requires in the field.
There would be 2 different Access applications on the laptop.
One would work with the data on the laptop and allow them to update the
information as required. This would not require a link to the
The second application would use linked tables from the repository db
to "synch" the data. This would be a manually initiated process but
that's ok. This would involve queries to determine what data needed to
be updated back to the repository and what new data would be pulled
I've looked into replication but the addition of GUIDs and the
limitations imposed on the auto-number fields would make it a less than
- Prev by Date: Re: Parameterized Saved Sub Query
- Next by Date: Re: Partially Disconnected Databases
- Previous by thread: How to set up an Option Box?
- Next by thread: Re: Partially Disconnected Databases