Best methos of deplying database

[hawg1]

All,

I have modified the call tracker database template to the suite my needs but one issue has arose that I'm seeking inputs on how to handle.

I need to have three copies of the database running on three seperate computers (one being the master), all will be at diffferent locations. Network connections will be zero as certain security protocols/network availablity will prevent it.

What is the best method to handle this? I have read about splitting the DB into a FE and BE, but those require the use of a network. I require a means that two individuals at different sites can use their copy of the database to make data entries and allow a third person at a third location to collect the data from the previous two and merge into one database.

Ideas?

 

[JANR]

If you have pre access 2007 you might look into Replication.

http://en.wikipedia.org/wiki/Replication_(computer_science)

David Fenton is the real expert on this forum on this subject, he might check in later. If you are using later versions accdb, then perhaps Sharepoint is a way to go.

JR

 

[dfenton]

If you have no network connection at all, none of these usual options are available (in descending order of preference, in my opinion):

1. host the app on a Windows Terminal Server available to all (requires full-time Internet connection).

2. deploy using Sharepoint (requires ability to connect to Internet long enough to synch up the local data to the Sharepoint server).

3. use Jet replication (requires the ability to connect via some form of SMB networking, either directly on the same LAN, or across the Internet or a WAN over a VPN -- if there's never any network connection other than "sneaker net" then Jet replication cannot be used).

If none of those are available, then you have to manually program some method of synchronizing the data. This is not a triviality, particularly if users are adding/deleting/editing records in all three copies of the database.