>"Challenging" is putting it mildly. I take this approach: I use unique
>IDs, because I need the performance, but 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.
That's a good idea. Wish I had thought of that before I wrote all my
uniqueID code, found out that the IDs are not guaranteed persistent, and
rewrote everything to use record IDs. :-)
Regards,
Steve Mann
-------------------------------------------
Creative Digital Publishing Inc.
1317 Palm Street, San Luis Obispo, CA 93401-3117
-------------------------------------------
805.788.0138 805.593.3811 (fax)
[EMAIL PROTECTED] http://www.cdpubs.com
