Wow, intriguing problem. If I were teaching computer science I might even assign something like this as homework.
Keeping each class in a separate database is messy. This forces you either to build and maintain a list of the classes, or to iterate over all databases each time you want to draw the list of classes. Switching from one class to another requires a DB close/open, with any initialization/setup overhead too. And think of the support issues--how many files do you think your customers can install without calling your help number? How do you structure your conduit/synchronization? Better to have a class DB (one record per class) and a student DB (one record per student). You'll need some common information to "JOIN" (hint) the two kinds of databases together, something like a student ID number. Then some way to mark which students are in which classes. You could list all of the students in each class's record. Or list the classes each student is taking in the student's record. Or you could do both. Your choice will make some operations faster and others slower, and will require different amounts of memory; you'll have to decide which parts you want to optimize. Enough hints? H -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
