Well 14 tables raises a new concern. You can only have 16 categories in a
Palm database. If you were to add a couple more tables to your already
extensive database you'll be out of luck.
Having multiple handles open at the same time is not an issue in itself.
It's not like an Oracle or Sybase database where you have to be concerned
about a limited resource such as database connections. The only issue with
that is managing 14 DmOpenRefs instead of just one.
One other reason to use separate Palm databases for each table is that it's
more maintainable. For instance: Palm databases have a version attribute. If
you update your application and update one of your tables you can simply
increment that version attribute of the Palm database in new releases. You
can easily detect when a user has an old version of that table and upgrade
or delete it. If all your tables are in one Palm database, however, you only
have one version for all your database tables.
-Bob Whiteman
> -----Original Message-----
> From: K. Chugh [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 27, 2000 11:26 AM
> To: Palm Developer Forum
> Subject: Re: multi table relational databases
>
>
>
> hi bob. thanks for the reply. i am looking at like 14 or so
> tables, and i figured i don't want all those handles open at the same
> time. this is my first database program so i'm not sure if
> this is a rational concern or not. some of the tables will
> have only a
> few records, while others will have as many as a few thousand
> records. do you think i should actually implement one database for
> each table instead of one database with a table id?
>
> thanks,
> kevin
--
For information on using the ACCESS Developer Forums, or to unsubscribe, please
see http://www.access-company.com/developers/forums/
