logo
search
Others

Fix Access 64-Bit Upgrade Returning Incorrect Query Results

WPS Content ManagerWPS Content Manager Sep 28, 2026 870 views

Question details

The user is experiencing incorrect query results, including wrong dates, amounts, and readings, after upgrading Microsoft Office from 32-bit to 64-bit.

Fix Access 64-Bit Upgrade Returning Incorrect Query Results
Product
Microsoft Access
Device & OS
not provided
Scenario
Running database queries that filter records using a date range after migrating to 64-bit Office.
Observed behavior
The query appears to ignore the requested date range (such as BETWEEN conditions) and returns records outside the specified timeframe, alongside incorrect numerical data.
Before you start

Ensure you have access to the original 32-bit database environment or documentation to accurately compare the underlying tables and query structures.

Solution 1Recommended

Compare Underlying Tables and Data Sources

Ensure that both the 32-bit and 64-bit versions are pointing to the exact same dataset, as data source discrepancies are the most common cause of differing query results.

Differences in table contents or query sources are far more likely to cause incorrect results than the Office bitness itself. When migrating environments, linked tables can sometimes inadvertently point to an older or alternate dataset.

1
Check Linked Table Manager

Open the upgraded database in the 64-bit version of Access. Navigate to the 'External Data' tab and click on 'Linked Table Manager'.

2
Verify Data Paths

Review the paths for all linked tables to confirm whether the source is a local Access backend or an SQL Server database, and ensure they match the 32-bit setup exactly.

3
Inspect Raw Table Data

Run a basic SELECT query on the individual underlying access-log and employee tables before they are joined. Verify that the raw data contains the correct years and records.

Compare Underlying Tables and Data Sources
Data Source Mismatch: If the 64-bit version returns older records, it is highly probable that the linked tables are pointing to an outdated copy of the database.
Free Microsoft Office alternative

Looking for a Lightweight and Free Office Suite?

While Microsoft Access is used for complex databases, WPS Office is a fantastic free alternative for your daily document, spreadsheet, and presentation needs. It provides seamless format compatibility and a familiar interface without expensive subscriptions.

  1. 1. Download the Installer: Visit the official WPS Office website and click the free download button.
  2. 2. Install the Software: Run the lightweight setup file and follow the on-screen instructions to complete the installation in minutes.
  3. 3. Open Your Files: Launch WPS Office and open your existing Office files directly with perfect formatting retention.
Highly compatible with Microsoft Excel (.xlsx), Word (.docx), and PowerPoint (.pptx) formats.Lightweight installation that runs smoothly on both 32-bit and 64-bit systems without slowing down your PC.Familiar, easy-to-use interface requires no steep learning curve.Built-in robust data management tools in WPS Spreadsheet for organizing large datasets easily.
microsoft office alternative - wps office

Frequently Asked Questions

Why does my query ignore date ranges after upgrading to 64-bit Access?

This is rarely caused by the 64-bit architecture itself. It usually happens because the upgraded database is accidentally linked to a different or older data source, or the system's regional settings affecting date formats have changed.

Will switching back to 32-bit Office fix my Access query issues?

If the issue stems from mismatched underlying tables or incorrect SQL Server connections, reverting to 32-bit will not solve it. You must ensure both versions are querying the exact same data source.

How do I verify if my Access database is connected to the right SQL Server?

Go to the 'External Data' tab on the ribbon and open the 'Linked Table Manager'. This will display all linked tables and their data source paths, allowing you to confirm if they point to the correct Access backend or SQL Server.