Articles in this section

See more

With Total Access Analyzer 97 I get Error 2450: "Microsoft Access can't find the form 'TAA_Reports' referred to in a macro expression or Visual Basic code."

Avatar
Technical Support
  • Updated
Follow

topbanner.jpgtotal-access-analyzer-med.gifaccess-documenter-access.jpg

Background

Total Access Analyzer is the world's leading Microsoft Access add-in product and designed to help you create better Microsoft Access solutions through comprehensive documentation and analysis. Total Access Analyzer offers more than 380 Reports, making it the most power documentation and analysis program for Microsoft Access professionals. 

Problem

With Total Access Analyzer 97 I get Error 2450: "Microsoft Access can't find the form 'TAA_Reports' referred to in a macro expression or Visual Basic code." 

Solution

With Total Access Analyzer 97 the error that you are receiving may be caused by one of the following issues:

Issue 1

Code in a module or a macro is pointing to a report that is not there. This implies that there is a broken VBA reference in code somewhere in your database. To resolve this problem, follow the steps to decompile and recompile your database, and run Total Access Analyzer again.

Issue 2

There is a space in the Hyperlink property of the properties of a control. To resolve this problem:

  1. Open the form or report with the name of the one in the Error log.
  2. Go to each control (most likely a Label control) to determine the properties of them and find one with a space (" ") in the Hyperlink or Hyperlink SubAddress property.
  3. Remove the space in that field.
  4. Compile and save all modules, and run Total Access Analyzer again.

Issue 3

This may be due to a bug in MS Access regarding checking attributes of a Crosstab query. When checking the attributes of a field in a Crosstab query, MS Access tries to actually run code that the data source uses to get its data when the data source is another query! Unfortunately, this is a bug in MS Access 97 and 2000.

This is a Microsoft bug that has been reported to Microsoft. In the meantime, the only available workaround is to not analyze the Crosstab queries that have relations to any query that uses the query "SelectQuery1". We highly recommend that you inform Microsoft of this issue as well, so that they are aware of the number of customers affected by this bug.

Additional Support Resources

download-trial-blue.jpg

Comments

0 comments

Please sign in to leave a comment.