Hi George:
 GC> Now for my question, which is the better method (and why)?
 GC> Put all related tables into one big database.
 GC>   It looks like this way only one call to use the 
 GC>   database loads everything.
For simple management of the tables, this is the easiest.
 GC> Put only each related set of tables into separate databases.
 GC>   Can use each database separately and may be able to 
 GC>   write separate modules without the extra overhead.
The next easiest to manage .... until a relationship changes connecting
tables from different .DBCs.
 GC> Non-related tables remain as Free Tables.
Ah, 1.x technology.  Actually, the advantage here is that other apps can 
directly read these .DBFs.  They cannot do so when they are in a .DBC.  The 
disadvantage is the data security and data integrity which must be programmed 
as you did in the early FoxBase.
David in Dallas.
--- Maximus/2 3.01
---------------