Syncmgr.h was, as I understand the process, accessed while the program was
compiling, not linking, and my problem was with a linker error.
Yes. The syncmgr.h file is for compiling, and the sync20.lib file (the one in
the CDK) is for linking, right?
> I don't understand the need to refer to "imperfect knowledge".
Because they didn't know anything about the DLL you were asking about. Had they
known more about it they would not have suggested that solution.
The IMPDEF program's .def file based on sync20.dll caused a problem with
specific, unknown function names.
Which makes me think that you shouldn't have been using impdef. That doesn't
produce anything you didn't already have, does it?
The restriction to a linker error suggests that the problem was in external
code references that the linker could not fill in.
Right, to the .lib files normally, yes?
I'm probably not the only one whose grown a little tired of this, so I'll
stop here, even if I must remain uncertain of the specific cause.
It doesn't really matter now, but I'd hate you to go around thinking you could
only write conduits using Visual Studio :-)
Thanks for the response.
No worries
Cheers,
Jim Cooper
__________________________________________
Jim Cooper [EMAIL PROTECTED]
Skype : jim.cooper
Tabdee Ltd http://www.tabdee.ltd.uk
TurboSync - Connecting Delphi to your Palm
__________________________________________
--
For information on using the PalmSource Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
