Re: Homegrown synchronization

rdemyan@xxxxxxxxxxx wrote in
news:1167172956.778272.263370@xxxxxxxxxxxxxxxxxxxxxxxxxxx:

It would seem that the only way to trim this execution time down
would be to write the record(s) to the temp updateDB table when
the record(s) are actually deleted. This might actually be a
possibility, since with virtually all table deletes, I use an
action query like strSQLDELETE = "DELETE *......". Of course,
I'm sure that there are probably a few exceptions, but still I'd
be able to find the vast majority very quickly and then simply
copy and paste the code and add a database qualifier to the
external table. I'm going to look at this since then I wouldn't
have to check for deleted records upon creating the temp updateDB
which would save at least 50 seconds of time.

The way I've done this in the past is to never actually delete
records, but just to mark them deleted. Then deletions are
propagated in the code the processes the updates. Your app then has
to filter out the records that are marked deleted.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
.

Loading