Justin,
Your table structure is incorrect and going to cause you numerous problems. If each of these tables has a primary key whose value is the same in each client related record of each table then this is not a unique identifier. It is the the same as having one table of records with 10 - 15 copies of a primary key.
I assume there are different Invoice Numbers to all these records and I would recomment using that as the primary key of a new table to which all records would be appended. These records would then be related to the client in a standard database design using the ClientID (PK) as a foreign key. See sample structure below.
tblInvoice
InvoiceNo (PK of this table)
InvoiceDetails
Amount
VAT
TotalAmount
ClientID (PK of tblClients and Foreign Key in this table)
If you could explain the reasons for the 10 to 15 tables we might be able to help you come up with a different solution.
BTW when I asked for table structure I was only looking for something like the above. I didn't need to see the actual data.
Mary
Unfortunately I cannot post the tables because they contain important client information which I cannot divulge.
Basically the primary key is linking all of these tables up in queries. I am working with a form to plug in client information into different tables. The primary key is the same for all of the tables and a single textbox in my form is where you enter the primary key. Just hoping that instead of having to enter the primary key in the form in different textboxes about 10-15 times (to enter them into each table) I was hoping that one textbox could link to 10-15 tables. I don't know if I can make it much more clear I can be.
Sorry that I cannot give you an example of the project that I am working on, but I am not allowed.
Thank You,
Justin Reneau