Re: OpenOffice, Go-OO, ODBC, Offline Data Entry

I faced a similar problem a while back.  The solution I came up with
is to have two extra columns - the first is a timestamp field, and the
second a last change field.  The timestamp field just records the date
and time of the last change, and the last change field records the
type of change - (A)dd, (C)hange, or (D)elete.  In this scenario,
deletes (if allowed) are just flagged but not done immediately, and
the active records are selected by simply doing a "SELECT * FROM blah
WHERE last_changed <> 'D'".  Of course, ofr this to work, each record
has to have a unique key - adding an IDENTITY field works nicely.

Synchronization is trivial at this point.  :)

-- 
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe:    http://lists.mysql.com/[email protected]