My last post proved to be partially wrong. Installing to the Palm
directory didn't fix our HotSync freezing problem - see below.
We recompiled our project using VS 2005 (code is written in C#) and
CDK 6. It now runs fine on Windows XP (Palm Desktop 4.1, 4.2 and 6.2)and Windows Vista (Palm Desktop 6.2). The biggest challenge we have had has been with the version of ComConduit.dll and Interop.PDDirectlib.dll and Interop.PDStandardlib.dll. You should not replace these files with your installer, neither should you put older versions of dlls(4.X) in your application folder if you are using a newer version of Palm Desktop and HotSync Manager.
Our application has around 30 pdb files and we found that the .NET
Garbage Collector (GC) was coming around a little early and cleaning up database connector objects before we were done with them. We discovered if we disabled a number of conduit classes(processing their respective pdbs) that the conduit stopped stalling HotSync Manager. It was not one specific class but rather
the sum of a certain number of them that caused the issue. We had
to find a way to manage when the GC would run. Now our conduit is no longer causing HotSync Manager 7 to freeze after our conduit closes.
NOTE: You do not need to install Palm COM Support with HotSync Manager 7 or 6 as it is built into the Palm Desktop installer - see Wayne's quote of the docs.
We are using CDK 6 for all HotSync versions now and so far things
are going well with that. I suggest recompiling with VS 2005 and CDK 6. It should just work. The libraries in the CDKs aren't versioned but the files installed with Palm Desktop are. We did not
rewrite our conduit using API methods that were new in 6. We just
recompiled using the CDK 6 reference.
If you are using methods new to the CDK 6 API it is obvious that
those methods will not work in a pre-HotSync 6 environment as Wayne has quoted from the docs.
For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/