Hi can anyone give me some ideas of how to organize my database(s)? I have in mind keeping track of a large indeterminate number of small transactions (say less than 4 bytes). I assume that it would be incredibly wasteful to allocate each of these transactions to their own record. So I suppose I will pack a large number of these transactions in a record. Is it good practice (design) to store the transactions in one database, and pointers to the start and transaction record index and their offsets in another database (my app may need transactions from several records)? Or is there a simpler method?
Dwayne Fujima [EMAIL PROTECTED] -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
