This is a general question regarding a main database (table) and a related child database (table).
If one were to create a relational database in a database program such as Access one would make sure that the information gathered from the main table was unique. I can create an auto incrementing value that would be saved in the main database and take that value and save it in each of the child database records thus creating a linking value. This is not a problem. But the other values within the main database (when evaluated as a unit) need to be unique (compound key). The only way I can conceptually visualize insuring a compound key is unique is by iterating through and checking all the values before a record is saved in the main database. Am I asking Palm to do more than it was intended or am I overlooking the obvious. In addition, when user switches from the main database to the child database one would prefer to see only those records related to the main database linking value of choice. In a database program such as Access one would just create a recordset from a query involving those linking values. Again, is this something I should stay away from or am I overlooking the obvious. If worse came to worse, I can always do some quality control after the data has been downloaded from the palm to a text file. Your insights are appreciated. Jay -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
