distributed solutions

[Guest_imported]

We have authored a VB application whose backend id SQL Server. In some cases we would like users to continue to work even if the LAN is down. In other cases the operator might what to take work home or off site. In ether case we need the operator to work off-line.

We have a few thoughts as to how we can do this, and I would like to hear how others have architect distributed solutions. Some technologies under discussion are:

- An SQL Server DTS export to Access when the user logs on.
- Using MSMQ to process transactions.
- Forcing a user to check-out (bring local) a record for working off-line.
- Replication

 

[foxdev]

Of the choices, replication seems the easiest. Another option would be to run MSDE on the individual machines, with an Uploaded flag column on each table that is transactional. When connected, a job could run that uploads all new/changed records. This doesn't account for the fact that more than one user may have changed the record, though.

The party line answer I think would be replication, using GUID columns instead of Identity columns as keys where needed. Robert Bradley
Sr. DBA, some big company
cheap prints and oil paintings:

http://www.lowcostprints.com