RE: [coldsync-hackers] Re: finding a suitable record id for appendrecord

["Brian Johnson" <bjohnson at jecinc dot on.ca>]

Most of my conduits are combination fetch and dump with the generic sync
conduit doing the transfer work

Following the concept of Coldsync, it allows the Palm to be removed faster


-----Original Message-----
From: owner-coldsync-hackers@lusars.net
[mailto:owner-coldsync-hackers@lusars.net]On Behalf Of Alessandro Zummo
Sent: Tuesday, April 16, 2002 9:56 AM
To: coldsync-hackers@lusars.net
Subject: [coldsync-hackers] Re: finding a suitable record id for
appendrecord


 On 16-Apr-02 at 13:37:08,
  Brian Johnson <bjohnson@jecinc.on.ca> wrote:


> I keep running into the situation where I need to know the record id of a
> new record I'm adding (to track it for syncing to another data source)

> But I'm starting to get into a conduit where I realistically could very
> quickly get to uppermost id number (around 32000 isn't it - it was post

> SO .... I was wondering if we could work together to get a working routine
> that everyone could use as needed

You may want to use a sync conduit and communicat to the palm
directly. Then, when you add a record, you'll get back it's id.


--

  - alex.



--
This message was sent through the coldsync-hackers mailing list.  To remove
yourself from this mailing list, send a message to majordomo@thedotin.net
with the words "unsubscribe coldsync-hackers" in the message body.  For more
information on Coldsync, send mail to coldsync-hackers-owner@thedotin.net.


-- 
This message was sent through the coldsync-hackers mailing list.  To remove
yourself from this mailing list, send a message to majordomo@thedotin.net
with the words "unsubscribe coldsync-hackers" in the message body.  For more
information on Coldsync, send mail to coldsync-hackers-owner@thedotin.net.