You might be able to use a union query. I question why you need different
tables for different tools. This doesn't sound like the table structures are
normalized.
Can you share your reasons for separate tables as well as your current table
structures?

Signature
Duane Hookom
Microsoft Access MVP
Well as there are 9 different types of tools, as in Hydraulic,
Pneumatic, Eectrical, Welding, Precision, Safety Equipment, Lifting
equipment and Fire Extinguishers, I thought it best to have a different
table for each type.
Basiclly each table consists of 10/9 fields:
ID
Manufacturer
Product
Size
Asset No
Serial No
Last Test Date
Next Test date
Location
Notes
I don't know if they are normanlised or not but they are related.
Thanks
> You might be able to use a union query. I question why you need different
> tables for different tools. This doesn't sound like the table structures are
> normalized.
>
> Can you share your reasons for separate tables as well as your current table
> structures?
Douglas J. Steele - 30 Nov 2008 21:32 GMT
If all of the tables have the same fields, then there's no reason to have
separate tables for them. Just add another field that identifies the type of
tool, and use one table for all of them.

Signature
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)
> Well as there are 9 different types of tools, as in Hydraulic,
> Pneumatic, Eectrical, Welding, Precision, Safety Equipment, Lifting
[quoted text clipped - 21 lines]
>> are normalized. Can you share your reasons for separate tables as well as
>> your current table structures?