I'm glad you're speaking for yourself. Our latest creation does not use conduits directly. We read and write directly to PDB files. And its not a hack (Palm published the PDB/PRC file format) or some thrown together kludge. Infact, the app is more complex than any conduit I ever wrote. We required integration to potentially dozens of different database formats. Reading the PDB files directly allows our customers to customize the PC side very quickly and without the need to 'understand' conduits (not to mention they don't require a $5,000 Hotsync server license) There's nothing wrong with reading PDB files directly. Especially now that Palm supports the file format. FYI: Conduit support problems seem to take up about 75% of our support time. Our latest app that works directly with the data files (and may be an order of magnitude more complex) and has required very little support time.
> > Here's one management might understand. Personally, I view apps that > access the PDB directly more like a hack than a real app. I get the > feeling that the people who wrote them just didn't feel like putting > forth the effort to do it "right", so they hacked it instead, and, > this might reflect in the rest of the application as well. > > That's not to say those apps actually *are* subpar, but that's a > feeling I get when I hear that an app is accessing things directly. > It might turn off other people too. > > Having learned conduits, I understand the aversion to them. You get > to write a nifty little PalmOS app that works very nicely and has a > nice development kit, but then you also have to write a conduit on a > kludgy system (Windows), and you also have a completely different set > of support issues. -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
