TableSiteSheet
number (as primary key)
other fields
TableLocationSheet
number (connected with TableSiteSheet)
PK (for each table)
Language (text)
other fields
And other 17 tables like these
Just let me clarify this.. there are 17 tables like TableLocationSheet (same fields just different language and other info) ?
Can these not be put together into one huge table?
TableLocationSheet
TableLocID - PK
SiteNo - long (connected with TableSiteSheet)
Language (text) <<
Put these into another table and use an ID to link?
other fields <<
these are other associated data fields for this record
As to the forms, you are doing a search on one, then for each successive return you are filtering further each time on the returned subset of data from the previous query (deeeeeep breath).
So I gather that you need to select different records depending on criteria.
Possibly use a form to enter filter data on to then use this data to filter the main records and return only one query with lots of where clause sections. You may want to investigate this. Also you may need to look at the table layout again and see if you can simplify it more. (read up on normalization)
Temp Table
1) Ok, copy the location table, call it TableTempLoc or something.
When writing the Sql Query/using the builder, change the type to Insert Into (addition or something along those line) and choose the TableTempLoc as the destination. Match up the fields, then when you run the query all the matching records are put into the TableTempLoc.
Then you can open a form based on that table to see the results.
Note: Each query that is run is filtered slightly differently and there is a possibility of duplicate records.
2) Another Idea is to dump in the records that match into TableTempLoc then delete the ones you aren't interested in - since its a copy of the data this means a smaller table at the end. It does however mean a huge mdb that will require recompacting afterwards.
Vince