I don't know if this is the best forum to ask this question, but I thought perhaps somebody here could at least point me in the right direction.
I am looking to create an application (Win32 at least). This app will need the ability to write to a central database, but also be able to pull a snapshot of that database into itself for remote (i.e., can't access the database) operation. I anticipate that the local user will modify the local copy, then sync that copy to the server. Concurrently, I anticipate other users will be modifying the server copy and/or their own local copy. The question I have is how to keep all this going without causing data loss? I mean, I can't run an auto_increment because the record numbering on the remote and server copies would be in conflict. I also am not sure of the best way to re-sync. I once was on a project where we logged all database entries, as three servers operated without being able to directly share (long story). The logging was problematic to say the least. I would say that if it were possible to have all of the functionality of a database with the version control power of CVS (or subversion), that would be ideal. Any suggestions? Regards, Ben Wilson -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
