Hi Alan,
Just a thought, Version 3 supports an additional entry point 'CfgConduit' as
well as the 'ConfigureConduit'. Thus Version 3 will look for the entry point
'CfgConduit' and call this in preference if found. If not it backs down to
the 'ConfigureConduit'. Version 2 only supports the 'ConfigureConduit' entry
point and calls this even if you supply the 'CfgConduit' entry. If your code
is implemented in the Version 3 only entry point 'CfgConduit' and nothing
has been implemented in 'ConfigureConduit' then Version 3 will work fine and
Version 2 will not.
Neil,
----- Original Message -----
From: Alan Macy <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: 19 May 1999 14:38
Subject: HSM 2/HSM 3
> My conduit, created with the new CDK version 3.0, works fine with HotSync
> manager 3, but, at least some of the time, is not called when the user has
> HSM 2 installed. For example, if the user clicks Custom... then selects my
> app and selects Change, nothing happens.
>
> Is this how it's supposed to be? For now, I'm telling my users to upgrade
> to HSM 3, but I'd like to avoid that.
>
> Is there anything I can do to make it work with HSM 2?
>
> I know this is a conduit question, but I can't seem to get any action over
in
> the conduit forum.
>
> Thanks,
>
>
> - Alan Macy
> http://www.ResponsiveSoftware.com
> Time and Billing for Consultants and Others
>
>
>
