Fix an Access Make Table Query That Creates a Huge Database
Question details
The user needs to combine three zone tables in an Access Make Table query without creating an excessively large database.

- Product
- Microsoft Access
- Device & OS
- not provided
- Scenario
- A Make Table query combines Zone 1, Zone 2, and Zone 3 into a Conditions table.
- Observed behavior
- The query becomes unresponsive and the database grows dramatically because the tables are combined without join conditions.
Check that the Date and Time fields in all three zone tables have compatible data types and matching values. Check whether each date-and-time combination is unique in each table, since duplicate matches can still multiply rows.
Join the zone tables before creating the Conditions table
Use this method to create a table containing rows whose Date and Time values match across all three zones.
Listing tables in the FROM clause without join conditions produces a Cartesian product: every row in one table is combined with every row in the others. Joining on both Date and Time limits the results to matching records.
The example selects fields from Zone 1 and Zone 2 while using Zone 3 to restrict the results to matching records. Add the required Zone 3 fields to the SELECT list if you also need them in Conditions.
In Access, open the existing query in Design View, then choose View > SQL View.
Replace the SQL with the following example, adjusting field names if necessary: SELECT [Zone 1].[Date], [Zone 1].[Time], [Zone 1].[Zone Temp 1] AS [Zone 1 °F], [Zone 1].[Zone Humid 1] AS [Zone 1 %Rh], [Zone 2].[Zone Temp 2] AS [Zone 2 °F], [Zone 2].[Zone Humid 2] AS [Zone 2 %Rh] INTO Conditions FROM ([Zone 1] INNER JOIN [Zone 2] ON ([Zone 1].[Date] = [Zone 2].[Date]) AND ([Zone 1].[Time] = [Zone 2].[Time])) INNER JOIN [Zone 3] ON ([Zone 1].[Date] = [Zone 3].[Date]) AND ([Zone 1].[Time] = [Zone 3].[Time]);
To preview the results without creating a table, temporarily remove the INTO Conditions line and choose View > Datasheet View. Check the row count and confirm that the dates and times match as expected.
Return to SQL View, restore INTO Conditions, and choose Run. If a Conditions table already exists, inspect it before deleting or renaming it; a Make Table query cannot create another table with the same name.

Append joined results to a predefined Conditions table
Use an Append query when you want to define the destination fields and their data types before adding records.
Work with exported Access data in WPS Spreadsheets
WPS Office is a free, lightweight alternative for everyday document and spreadsheet work. Its familiar interface and Microsoft Office format support make it easy to move exported data into a spreadsheet, although it does not fix or run Access queries.

Frequently Asked Questions
Why did my Access query produce so many rows?
Tables listed together in the FROM clause without join conditions form a Cartesian product. Join the zone tables on both Date and Time to restrict the results to matching records.
Why are some dates missing after I add the joins?
An INNER JOIN returns only records with matching Date and Time values in all joined tables. Check the source values and field types, or consider a different join type if unmatched records need to be retained.
Can I run the Make Table query again if Conditions already exists?
Not under the same table name. Inspect the existing Conditions table, then rename or remove it before rerunning the Make Table query, or use an Append query to add records to an existing table.
How can I reclaim space after removing unwanted query results?
After the query has stopped and you have removed unwanted tables, use Database Tools > Compact and Repair Database in Access. You may need exclusive access to the database.
Can WPS Office run the Access Make Table query?
No. Correct and run the query in Microsoft Access. You can export the resulting data to an Excel-compatible file and open it in WPS Spreadsheets for further review.




