If your database scheme is not complex and if you're up to it, you can treat
each record as a "database".
(ie divide up the Palm record into multiple custom DB's and records). Of
course, it's your responsibility to interpret the data. In the end you'll
just have one Palm database that will contain all your data.
Your record structure could look something like:
typedef struct {...} rectype1; // record structure for database 1 (Note:
ensure proper byte aligment)
typedef struct {...} rectype2; // record structure for database 2
typedef struct {...} rectype3; // record structure for database 3
typedef struct {...} rectype4; // record structure for database 4
typedef struct {
int num_recs1; // number of records in database 1
rectype *r1; // List of records in DB 1
int num_recs2; // number of records in database 2
rectype *r2; // List of records in DB 2
int num_recs3; // number of records in database 3
rectype *r3; // List of records in DB 3
int num_recs4; // number of records in database 4
rectype *r4; // List of records in DB 4
} customrec;
-Ken
> ----------
> From: Jeremy Nuss[SMTP:[EMAIL PROTECTED]]
> Reply To: Palm Developer Forum
> Sent: Wednesday, June 27, 2001 5:51 PM
> To: Palm Developer Forum
> Subject: RE: Database woes, need some advice
>
> >Why not just put each session in a separate record, avoiding the 15
> category limit?
>
>
> Each session will have a multitude of records associated with it across 4
> databases.
>
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe,
> please see http://www.palmos.com/dev/tech/support/forums/
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
