The following are two of the most common problems you may come across when debugging a conduit.
A problem that you might encounter is having a conduit that appears to be installed but doesn’t get called during a sync session. First, check the presyncing setup by choosing the Custom menu of HotSync. If your conduit doesn’t show up in the list, check the items in the following sections.
If you use a release version of one with a debug version of the other, the conduit is not called. Make sure that a debug version of your conduit is linked with debug versions of the DLL and that release versions are linked with release versions.
If you provide a full pathname for your conduit, make sure it’s
there. If you specify only the conduit name
MyConduit.DLL), the conduit must be in the DLL
path (a common place to put it is in the same directory as
Select the conduit and press the Change... button to have your ConfigureConduit routine called. If it doesn’t work—you know because your ConfigureConduit dialog doesn’t appear—here are some possible reasons:
Check that your
(or, for HotSync 3.0, CfgConduit) routine is in
your conduit and declared as
Also, make sure that the following are present and exported: