> > Could you explain how you deal with the syncing issues (when the PDBs > get transferred etc)? Do you have performance issues/workarounds for > large databases?
My data is small so I've never had to deal with any of the memory issues (typically < 5K per PDB) But I do sometimes deal with dozens to hundreds of individual PDB files. We use the backup conudit to bring the PDB files to the host platform. If any files need to be sent to the Palm, we use the standard install method. We do not need to 'sync' data, only to have it appear on the host. Thus, we don't benefit from syncing. > > Your customers are programmers? Or is your app customisable by the > users? IS departments mostly. So yes, they do some custom programming to read the data, but ultimately don't need to know anything about the Palm work with the data. > > Sounds like an interesting solution, if you're allowed to share any > details with us? > No real details to share. Backup conduit brings the data files to the host. Then you read PDB files directly. Customer sucks data from the PDB into their application format (which is not always a DB app) On the surface, its much less complicated than using a conduit, but we've had to do more work to make the transition seemless. There's nothing wrong with conduits. Just in my case they were more of a support black hole. > Cheers, > Jim Cooper -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
