At 10:23 AM 26/09/2001 +0100, Philip Sheard wrote:
> > I understand that the purpose of DmDeleteRecord (and DmArchiveRecord)
> > is to allow a desktop conduit to propagate the changes to desktop
> > applications. But what if I wrote a conduit for PC only but not for a
> > Mac (or users just doesn't want to install the conduit). So, would
> > there be any problem if we use DmDeleteRecord to delete a record but
> > user rely only on the backup conduit? Would the database header get
> > saturated with deleted record info and not allow any new record to be
> > created? What would the Palm OS do in such case?
>
>You could consider detaching records instead of deleting them.
I'm not too sure how that will help. I'm trying to do ultimately is to
write a PC conduit. Which mean I should be using DmDeleteRecord (and
DmArchiveRecord) instead of DmRemoveRecord so that my conduit can propagate
the info to the desktop app. But I'm a little concern about Mac (and
Linux) users who won't be using my PC conduit. I'm wondering if it would
cause them problem if I'm going to distribute the same app or if I should
write another version of the same app (that uses DmRemoveRecord to delete
rec) for people who rely purely on Palm's backup conduit. I tried to find
info in the docs about this particular case, but come up with nothing. Are
there any official word about this case?
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
