In one of my databases, there's a field that is used only on the Palm
device.

When the field is updated, I release the record with DmReleaseRecord(...,
false) so that the record is not marked dirty.  I want to reduce the
possibility of a collision during sync if the corresponding record on the PC
is modified.

Here's the problem: the database is not backed up by the Backup conduit
during hotsync, and if the user restores from backup, they don't have the
latest value in the Palm-only field.

I have the backup bit set in the database header, but this only causes dirty
databases to be backed up.

Is there any way to mark the database dirty and cause the backup conduit to
do its thing?  I found the dmHdrAttrAppInfoDirty bit, but can't find any
documentation about it.

Thanks,
David Kendall
[EMAIL PROTECTED]



Reply via email to