From: "Jim Cooper" <[EMAIL PROTECTED]> > > That's one less thing the maintenance developer has to learn. > > Well, you take away one thing and add another - you have to get at the > data in the backed up pdb file somehow :-) If you need to sync/transfer > data you need to write that piece somewhere. > I'll happily admit that my experience here might be several years out of date but, as far as I could tell, the code you pointed to requires Delphi while the approach I'm proposing only requires the tool to unpack the pdb. It's not so much the complexity of the coding, I agree that the code you've presented is easy to grasp, but it binds the project to Delphi. If I build a project for a client using a free pdb-to-csv unpacker I can include a batch file to do that task and the client has everything they need. I was never really happy with having to install an entirely different development environment just to compile the page of code that does the sync.
It's probably just be a matter of personal preference. Certainly for any developer already working in VS or Delphi it's no issue at all. > A conduit doing a one way sync to a CSV file takes a few minutes to > write, so it's not a big deal. Example code is here : > > http://www.tabdee.ltd.uk/Downloads/Demos/Demos.html > Chris Tutty -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
