>I have 8 structures and my original design called for 3 databases. How
>do you deal with different types of structures within the same
>database?
Here are three possiblities:
1 - If you're not using any categories that the user can see or
change, you could always make each of your record types a specific
category and use the various category-oriented database APIs.
2 - You could also put a tag field in each record indicating what
type of record it is and extract it's fields accordingly. That
doesn't give you any maintenance info (like how many records of a
certain type), but if you don't need that, it works OK. You could
also keep some of that type of info in the AppInfo block if you want
to take the time to track and update it.
3 - You could also put each record type in its own database instead
of your original 3-database scheme.
I've used all three approaches. #2 seemed like a good idea at the
time, but the code can get convoluted. #1 works well in certain
circumstances, but poorly in others. #3 is simple, clean, and
straigthforward, but you have to deal with more databases, database
references, and so on.
Regards,
Steve Mann
--
-------------------------------------------
Creative Digital Publishing Inc.
1315 Palm Street, San Luis Obispo, CA 93401-3117
-------------------------------------------
805.784.9461 805.784.9462 (fax)
[EMAIL PROTECTED] http://www.cdpubs.com
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
