I'm looking at an app that will have an online component and an offline one. Does anyone have any favorite references for what to do to keep the data reasonably close to in sync?
I'm thinking that people would have to download the data to their laptops, make the changes, and then upload the changes at the end of the session, checking for duplicate info and resolving any changes that were made. That would mean maintaining a separate audit trail for upload, I guess, rather than waste the time pushing unchanged data back up to the server. Or is there something I'm really blatantly missing here? (SQL Server replication, for example, if that's reliable enough.) _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
