Products & Services
CA! Access File Comparison Tool
Nov 2025 Ver.Up!
What would you do in such a situation?
-
Some problems occurred when a few or more persons were doing a system development together or using the developed system.
Its version control was in place, but only the Access file itself was committed, so it is unclear when or who created the trouble section. -
A problem occurred during the operation.
However, the development team cannot reproduce the issue, but it occurs in the Access file of a specific user.
It is unclear what the difference is. -
The print results of reports created by duplicating them are a little different.
The exact cause cannot be found. - You want to create documentation such as form design specifications, but is the only option to copy and paste or manually enter each form list and property one by one?
Feature Overview
Displays differences in properties and VBA code for each section, control, and procedure in forms, reports, and modules (VBA) in a tree view and list.
You can filter and sort to check the specific areas you need.
You will not need to open multiple Access files side by side to compare changes.
Export differences in forms, reports, and modules (VBA) to an Excel file as a list.
Useful for creating design documents, development, and version control.
Use Cases
As a version control assistant tool
When managing Access files directly with Git, use this tool to find differences between versions.
You can output the differences between before and after each important change to an Excel file and manage them with Git.
This makes it more easily to track change history and quickly identify and correct incorrect changes.
To investigate the cause of bugs
Easily check whether bugs that occurred after development release were caused by users changing properties or VBA.
You can compare the Access file at the time of release with the Access file where the bug occurred using this tool.
Not just properties
Conditional formatting, report grouping, sorting, and aggregation, as well as binary data (images, etc.) can also be compared and exported to Excel file. (Binary data can be exported to Excel for only comparison purposes.)
Documentation
In addition to lists of forms and reports, you can also export control properties to Excel file in a list format, making it easier to share design details with your team.
Review for VBA code
This makes it easier to find unnecessary events that tend to occur during use.
For example, you can find Sub procedures created with default names such as “Label1_Click()” , and are no longer linked to the changed event names after the control names were changed.
Additionally, when moving the positions of Sub procedures or functions within a single module, you can verify that the content has not changed due to operational errors.
For debugging and troubleshooting
By confirming changes to form or report properties, you can more easily identify the cause of bugs.
This is particularly useful in large projects, where it can be difficult to pinpoint which change caused a problem.
Screenshot
About this tool
Compare Access files and see differences immediately!
You can also export to Excel files for use with version control tools like Git!
You can save time and effort by quickly identifying which properties or macros (VBA) have been added, deleted, or modified, and view the values before and after changes.
Access files are automatically saved even if you don’t change anything at all.
So it is impossible to determine whether changes have been made based solely on the file's update date or size.
Therefore, the only way to identify changes to forms or reports is to manually review the property list.
With this "CA! Access File Comparison Tool" such manual verification is no longer necessary.
We highly recommend this tool to Access developers and all users.
Download (zip file) 
Manual (PDF file) System Requirements
- Windows 11 Pro version 24H2 or later (64-bit version)
- Microsoft Access 2024 or later or Microsoft 365 (version 2508 or later) Desktop Edition (Quick-to-Run or MSI Edition)
- .NET Framework 4.8.1 or later
Note: We may be able to accommodate requests for use in environments other than those listed above, changes to the list output method, etc. Please submit your request using the inquiry form below.
Limitations
-
In the current version, the comparison is limited to forms, reports, and VBA (modules).
Tables and queries cannot be included in the comparison. - The "Instancing" property of class modules (whether the class is "PublicNotCreatable" or "Private") cannot be retrieved.
- Files larger than 50MB cannot be compared.
- We have not verified compatibility with Windows 11 Home.
- Windows 10 and Access 2019 are no longer supported by Microsoft, so we cannot guarantee their operation.
Usage Fees
Free of charge for both corporations and individuals.
By purchasing a license, you can change the feature limitations shown in the table below.
To purchase a license or get Trial Edition, please visit My Page .
| Plan Name | Fees | Functional Limitations | Time limit |
|---|---|---|---|
| Free | Free | Limited | No Limited |
| Trial | Free | Limited | 10Days |
| Lite | 1,980JPY/M | Limited | 1Month |
| Pro | 2,750JPY/M | No Limited | 1Month |
| Pro 20-Days Pass | 2,200JPY | No Limited | 20Days |
| Pro 5-Days Pass | 880JPY | No Limited | 5Days |
| Plan Name | Access File Size | Object count limit* | Comparison | Export to Excel file |
|---|---|---|---|---|
| Free | ＜20MB | ＜20 objects | Only "All" | Not available |
| Trial | ＜50MB | No Limited | No Limited | Up to 500 lines |
| Lite | ＜20MB | ＜20 objects | No Limited | No Limited |
| Pro | ＜50MB | No Limited | No Limited | No Limited |
* All fees are inclusive of tax.
* The object count is the total of forms, reports, standard modules, and classes. Forms and reports modules are not counted.
* The fee is per user and does not renew automatically.
(Fees as of November 5, 2025)
Frequently Asked Questions (FAQ)
Basic Information
System Requirements and Installation
Features and Usage
License and Fee
Troubleshooting
Please install the desktop version (Click-to-Run or MSI).
If the “version number” of the installed Office includes “Microsoft Store” or “Windows Store,” you have the Microsoft Store version.
If it says “Click-to-run” or only the build number is displayed, it is the Click-to-run version.
Please check the version number by following these steps.
In older versions of Office, such as Office 2010, you can select these options during custom installation. If you are using Office in a corporate or organizational environment, please contact your IT administrator.
Reset the window size in the settings screen.
We have made every effort to prevent this from happening, but the VBA window must be displayed to obtain the code.
Other
Specifically, we are using the COM interface.
Those blogs or software use non-public APIs, so the results are not guaranteed.
We consider the use of such non-public APIs to be unacceptable for a product.
Release notes
Please read the Japanese version of the release notes.
