I'm at the mid-end point of my first Palm application. This app could be defined as a "database access app". My program presents forms to the user in which he can add and edit patient information, allergy info etc. Databases are "packed" ala string truncation etc. and linked via UniqueID's. There are more than 6 databases that are linked to each other (a relational database). I went with CodeWarrior and the PalmOS API (SDK 4.0) because my backround is in C/C++ and it was the environment which most reference manuals focused on.
After gaining some Palm programming experience and looking around several Palm related sites I've found several databasing utilities such as HanDbase, JFile and a whole bunch more. My question is this: Would it be wiser to use such an app. for a "Form and Database app." directed at the professional market or do these programs have shortfalls (need for Virtual Machine..licensing issues...performance problems etc.)? Obviously, ensuring referential integrity and traversing related databases is a top issue. It seems like the Database-Maker route would have cut development time down by a 1/3 to 1/2 the time it took to build this app up in CodeWarrior (of course, there was the learning curve with CodeWarrior... From now on I'll know what I am doing going into the project). Anyone ever played with these? Is there one that has established itself as a "standard" for PalmOS relational-databasing? bEN -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
