richard, >I was hoping to avoid this, as each list is 80.000 records as it is... why were you hoping to avoid this? what database are you using, and does it have a maximum number of rows? on most db's (even access) if you optimise your indexes properly the size of the table will not be a performance issue, and tables with millions or tens of millions of rows will function just fine. try it and see. >Will it be best to put all the pricelists into one big table, with >datefrom/dateto columns for each record, or to use a third table with the >datefrom/dateto columns, and link by tableID? yes, either would work. i'd recommend keeping everything in one place unless there's a compelling reason not to. simpler, and more elegant. hth, david -- If you are not the intended recipient of this e-mail, please preserve the confidentiality of it and advise the sender immediately of any error in transmission. Any disclosure, copying, distribution or action taken, or omitted to be taken, by an unauthorised recipient in reliance upon the contents of this e-mail is prohibited. Somerfield cannot accept liability for any damage which you may sustain as a result of software viruses so please carry out your own virus checks before opening an attachment. In replying to this e-mail you are granting the right for that reply to be forwarded to any other individual within the business and also to be read by others. Any views expressed by an individual within this message do not necessarily reflect the views of Somerfield. Somerfield reserves the right to intercept, monitor and record communications for lawful business purposes.