We received multiple customer reports that after Total Access Analyzer documents a database, it triggers an error when viewing the results. The message says:
You entered an expression that has an invalid reference to the property Form/Report
You are then forced to exit Total Access Analyzer.
The error is very strange because it seems to be caused by a memory problem that should not happen in the VBA code that Total Access Analyzer is running.
Since the problem occurs when viewing the results, one should not need to document a database before viewing it. Just viewing the documentation in the TDB file triggers the error.
Reboot to View Results
Multiple customers report that once the error occurs, it doesn't matter what Access database they open or what documentation they view, the problem continues until they reboot. Exiting Access and restarting does not make a difference which is very strange. After rebooting, most can view the results when they open a blank database and launch Total Access Analyzer. But that is very unexpected behavior.
Cannot Replicate Error on Another PC
Multiple customers cannot replicate this problem when they perform the same steps on another PC. On the second PC with the same versions of Microsoft Access and Total Access Analyzer, they successfully document the same database and can view the results.
While the database may be identical, different updates of Windows, Office, and other dependencies make it difficult to know if two PCs are truly identical. Something clearly isn't, but we have been unable to determine the difference.
Some customers reported that the problem went away after being an issue for many months. Total Access Analyzer did not change, so we do not know what made the difference.
We are Unable to Replicate the Error
Thank you to the customers who gave us their databases to test.
Unfortunately, we remain unable to replicate this problem in our environment across multiple PCs. That makes it very challenging for us to address.
Most Likely Cause: Database Corruption
The database being documented seems to be corrupt when this error happens. We suspect it is a combination of the database and that PC's Windows environment.
It is odd that a database corruption error wouldn't cause the documentation process to fail. So fortunately, the documentation is generated and can be viewed after reboot.
To address the database corruption issue:
- Create a new database
- Import all the objects from the original database
- Compile the database to make sure it works
- Compact the database then exit Access
- Restart Access and open the new database.
- Run Total Access Analyzer to document that database and view the results
So far, all customers who have tried this no longer experience the error.
Please let us know your situation, especially if you experience different results.