Re: Homegrown synchronization

2. use DAO to walk the recordset fields to find updated records.
This is a matter of writing on-the-fly SQL that is something like
this:

UPDATE table1
INNER JOIN table1 ON table1.PK = table2.PK
SET table1.field = table2.field2
WHERE table1.field <> table2.field2


For importing from the temp updateDB, I know which databases to use to
get table1 (currently connected backend file) and table2 (temp
updateDB).

But for exporting, this is not clear. The code will have created the
temp updateDB but it will be empty. I think I'm going to need to make
a copy of the backend file when the app opens. It will essentially be
a snapshot of the backend prior to any updates/edits/deletes.
Copying files on the local PC can be fast (75 MB on my machine takes
about 10 seconds). Then I need to do the join and update the temp
updateDB. I've never written code like that before but I guess if I
just change the Update statement above to:

UPDATE table3.....

table1 = local backend file table
table2 = copy of local backend file table created when app was first
opened during the session
table2 = temp updateDB table

There's probably more clever ways to do this, but this should work,
although speed is important.

.