I see information is stored in text files on desktop side most of the
times. Why the databases such as MS-Access or SQL server are not used as
often as text files. I 'll be implementing a conduit for an application.
If there are no precise reasons to use text files, I would prefer to use
Databases rather text files.
Veronica sent a marvelous answer, especially regarding the differences between the Palm "database" theory/structure vs SQL-type databases. She also suggests a two-step process: Palm -> text ->SQL database.
I would suggest backing up a few more steps in the analysis process to ask the question, "What is the purpose of this system?". IOW, what are the users' needs and requirements for this system to do? How is the raw information getting into this system and what are the users needed to find out from the processed information? On the desktop side, are there reports that the user will need to interpret the information or is the desktop app just a repository for the data? Basically, what are the users' requirements for the system you are designing? Usually with such a system the Palm device is only one piece of the puzzle.
Once the above analysis is complete, then the question of which tools to use to accomplish the task(s) can be answered more appropriately.
The systems that I have been creating tend to involve adding a mobile process to the data processing chain, working on existing data originating on either an AS400 or in a SQL Server database. These pre-existing requirements have suggested the selection of tools and the methodologies required to transfer and manipulate the required data between those repositories and the Palm/back again.
One last thing to take into consideration is the level of knowledge that potential users have (a nice way of saying "computer literacy"). Many of our users either use computers only because its a job requirement or "know just enough to be dangerous". If there's a way to break an app, some of them will find it like human Gremlins. Generally, therefore, we try to keep the user interaction down to a minimum. A two-step process like Veronica suggests does not work for us. Even with steps written down there have been users who will forget to do something in a process chain. For me, the KISS principal is still a good one to follow.
That my 1/2 cent on the question.
Steve Jerrett Systems Analyst
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
