Is it not possible that, as you are setting the
"unique" id on a record to it's old value, that it
will match the new "unique" id on a record that
you have not yet gotten around to fixing? Would
this cause problems in the indexing?
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi./sec ... not just a good idea, it's the LAW!
> -----Original Message-----
> From: Mark Nudelman [mailto:[EMAIL PROTECTED]]
>
>I also store a copy of the
> unique ID in the record itself. Then when my app receives a
> sysAppLaunchCmdSyncNotify, indicating a "restore" has happened, I run
> thru all the records and use DmSetRecordInfo to set the UID
> back to what
> it originally was.
