Total Access Analyzer
Frequently Asked Technical Support Questions

All Versions

• What version of Total Access Analyzer do I need? What versions of Access does Total Access Analyzer support?

• Can I try Total Access Analyzer before I buy it?

• How do I start Total Access Analyzer?

• Total Access Analyzer is not listed in my add-ins menu.

• Does Total Access Analyzer support Access Data Projects (ADPs)?

• How do I view or produce a list of unused objects?

• How do I save/print/export or output a report to another format?

• Will Total Access Analyzer make database changes for me?

• I get error number 2124.

• I get error 3163, "The field is too small to accept the amount of data you attempted to add."

• I get a different error (e.g. Error -2147417848, 6, 438, 2091, 2467, 3071, 3270, etc.) that is not listed above.

• I am getting an error:  The Add-In cannot be installed because it is missing a UsysRegInfo table.

Total Access Analyzer 2000

• I get one of the following errors:

  • Error 3024, "Could not find file '...\TA9DOC_T.MDA'."

  • Error 3734, "The database has been placed in a state by user '<name>' on machine '<name>' that prevents it from being opened or locked."

Total Access Analyzer 97

• When I run Total Access Analyzer, I get an out of memory error, but I have plenty of memory!

• I get error 2450, "Microsoft Access can't find the form '<name>' referred to in a macro expression or Visual Basic code."

• I get error 2188, "The object you attempted to load from text has an invalid value for the property 'Top' on a rectangle."

All Versions

What version of Total Access Analyzer do I need? What versions of Access does Analyzer support?

Total Access Analyzer is an Access add-in, and is Access version specific. For example, Total Access Analyzer 2003 will only work as an add-in through Access 2003.

However, Total Access Analyzer will document databases in any format that is supported by the specific version of Access. For example, Total Access Analyzer 2003 will document databases that are in Access 2000 format or Access 2002-2003 format, provided that the database is opened in Access 2003.

The following versions of Total Access Analyzer are available:

• Total Access Analyzer 2003  supports Access 2003.
• Total Access Analyzer 2002 supports Access 2002.
• Total Access Analyzer 2000 supports Access 2000.
• Total Access Analyzer 97 supports Access 97.

Check the Product Compatibility Chart for version information for all of our products.

Can I try Total Access Analyzer before I buy it?

Download the Trial Version to try Total Access Analyzer before you buy it.

Also, remember that FMS products come with a 30-day money back guarantee, so you can buy with confidence!

How do I start Total Access Analyzer?

The Total Access Analyzer is an Access Add-in program. To start the program, open your database, and select "Tools, Add-ins" from the Access menu.

You can view the help and README files by going to the Start, Programs menu.

Total Access Analyzer is not listed in my add-ins menu.

This issue can occur when Total Access Analyzer is installed using the Access Add-in Manager. Total Access Analyzer is designed to be installed by using the stand-alone setup file.  In order to install this product, please perform the following steps:

1. Click the setup file "setup.exe".
2. Follow the prompts of the setup routine.  Enter your key number when prompted.
3. After clicking finish to terminate the setup process, open your copy of Microsoft Access.
4. Open an existing database or create a new one.
5. Click Tools --> Add-Ins --> Total Access Analyzer.  Total Access Analyzer will then launch itself and display the main menu.

Additionally, please remember that each version of Total Access Analyzer is MS Access version specific and is not supported for use in other versions of MS Access. Below is a list of each version of Total Access Analyzer and the version of MS Access that each version of Analyzer is compatible with.

Total Access Analyzer 97   - Microsoft Access 97
Total Access Analyzer 2000 - Microsoft Access 2000
Total Access Analyzer 2002 - Microsoft Access 2002
Total Access Analyzer 2003 - Microsoft Access 2003

While the User Interface (UI) for each version of Total Access Analyzer is supported in the version of MS Access for which it was designed, please note that Microsoft Access 2002 and 2003 both support the Access 2000 and 2002 database formats.  Since this is the case, Total Access Analyzer 2002 can document the 2000 and 2002 file formats as long as you open the product within Access 2002.  Total Access Analyzer 2003 can document the 2000 and 2002 file formats as long as you open the product within Access 2003.

Total Access Analyzer 97, 2000, 2002, and 2003 can be on the same machine provided that they are installed in separate directories.

Those that have purchased an earlier version of this product are eligible for the upgrade price of the product when purchasing a newer version.

Does Total Access Analyzer support Access Data Projects (ADPs)?

Total Access Analyzer (version 2000 and later) supports documentation and analysis of MS Access ADPs. However because of the many differences between MDBs and ADPs and the way add-ins work with them, there are significant differences with the documentation Total Access Analyzer generates and the way it behaves.

Certain object types are similar between MDBs and ADPs. For instance, forms, reports, data access pages, macros, modules, and command bars are essentially the same and the documentation for those objects is similar.

Some objects only exist in one and not the other. For instance, queries only exist in MDBs, while ADPs have views, database diagrams, and stored procedures. Total Access Analyzer generates the appropriate documentation for all of these objects.

Both MDBs and ADPs have tables, but they are different. MDBs can link to tables or have tables stored within the MDB itself. ADPs only link to tables that exist on the server. The documentation of the tables is also slightly different. Fields in MDBs are called Columns in ADPs. ADP tables also have Keys and Triggers. Again, these are documented based on the database type.

Please refer to the user guide or help file (specifically the sections MDB vs. ADP Documentation and Documentation Limitations for ADPs) for details about documenting ADPs.

How do I view or produce a list of unused objects?

There are two ways to see this information:

1. From the Main menu, click on the "Explorer" Button. Click on the database (top level) in the TreeView. View the Suggestions tab. Unused objects are listed there. You can filter the list of suggestions shown by clicking on the Filter Items button. The types of unused objects include:

• Macro Unused
• Module Unused Class Property
• Module Unused Procedures
• Module Unused User Defined Type
• Module Unused User Variables and Constants
• Query Unused
• Table Unused

2. From the Main menu, click on the "Print" Button. The information is available under the Suggestions area of the reports (left side of the 2 panel form). There are specific reports in this section for unused procedures, properties, user defined types, and variables.

How do I save/print/export or output a report to another format?

Saving a Total Access Analyzer report in a different format is something that can be done, but does not always work for all reports. The ways to do this are below:

1. The best way to get the information in the same format is to use the Snapshot Viewer for Microsoft Access that comes with Microsoft Office Service Packs. This is the easiest.

2. You can also use a variety of other methods including the Options to Output reports to MS Word (Tools Menu | Office Links | Publish it with MS Word).

3. You can also Export the report to a different format as well. To Export, Go to the File Menu and click on Export. When the dialog comes up, you can choose to Export to many different formats (The box that says "Save as Type").

4. Lastly, while viewing the report, go to the file Menu and click on the Send option. A dialog will show asking what format you want to send the file in. Choose the format you want (***NOTE that all formats may not work properly with our reports). After you click OK, your default mail browser shows with an attachment. Simply save the attachment as "[What you want to name the report]" or e-mail the attachment to yourself.

These methods do not always work properly and some information may be missing or formatted incorrectly for how you want to view it. The formatting is due to the way that Microsoft handles the output of the fields or controls it finds. We have no control over this formatting or the output functionality since this is Microsoft Access functionality for outputting reports and not our own.

Will Total Access Analyzer make database changes for me?

Total Access Analyzer does not make changes to your database. Due to the nature of the issues detected, many items require the database developer or administrator to make decisions about what should be changed, and what impact the changes will have on the overall application.

However, Total Access Analyzer has many tools that make it easy for you to make the desired database changes. For example, the Documentation Explorer has a feature that lets you jump right to the object that triggers an error or other issue. Additionally, several reports are available that show details about what should be changed and how to change it.

I am receiving error number 2124.

This error is most likely caused by the Analyzer database being corrupted. Corrupt databases can occur for a variety of reasons. Below are the suggested steps to take regarding this error:

1. Uninstall Total Access Analyzer
2. Re-install Total Access Analyzer, and visit the Updates Page to download the latest update.
   If after applying the latest update you are still encountering errors, then please let us know so we can be of further assistance.
3. Run the Analysis again.

I get error 3163, "The field is too small to accept the amount of data you attempted to add."

This error can occur when there are names of objects that are extremely long. It can occur in a language version that uses very long words. The issue is that this information needs to go into a text field that has the limit of 255 characters. Because it is information that needs to be indexed, we cannot make the field anything except a text field.

Due to this limitation, the only workarounds available are as follows:

1. Rename any objects with long names to a shorter name.

2. If the Diagrams are not needed, then you can turn that option off.

I'm getting a different error that is not listed above.

The first step when you receive any error is to make sure you're using the latest version of Total Access Analyzer. Check the Updates Page, and make sure you have the latest update.

If you using the latest update, and you are still encountering an error, it may be caused by corruption or broken references in your database. This problem can manifest itself as one of the following errors:

• Error -2147417848, "Method '<Name>' of object <Name> failed"

• Error 6, "Overflow."

• Error 438, "Object does not support this property or method."

• Error 2091, "<Name> is an invalid name."

• Error 2467, "The expression you entered refers to an object that is closed or doesn't exist."

• Error 3071, "This expression is typed incorrectly, or it is too complex to be evaluated."

• Error 3270, "Property not found."

• Various other error messages.

To resolve these issues, follow the steps to decompile and recompile your database. This often fixes mysterious corruption issues related to VBA code.

Then run Total Access Analyzer again. It you still encounter problems, please contact us so that we can be of further assistance.

Total Access Analyzer 2000

I'm getting one of the following errors:

• Error 3024, "Could not find file '...\TA9DOC_T.MDA'. "

• Error 3734, "The database has been placed in a state by user '<name>' on machine '<name>' that prevents it from being opened or locked

To resolve this issue, please follow the steps below:

1. If you have had the Total Access Analyzer Trial version installed on your machine, use Add/Remove Programs to uninstall the Trial (Start | Settings | Control Panel | Add/Remove Programs).

2. After uninstalling the Trial, uninstall the Full version of the product.

3. After uninstalling both the Trial and the Full versions, browse to your installation directories, and delete the Trial and the Full versions' installation directories.

4. Re-install Total Access Analyzer, and visit the Updates Page to download the latest update.

5. Run Total Access Analyzer again.

If this does not resolve this issue, please contact us so that we can be of further assistance.

I receive error 3734, "The database has been placed in a state by user '<name>' on machine '<name>' that prevents it from being opened or locked."

To resolve this issue, please follow the steps below:

1. If you have had the Total Access Analyzer Trial version installed on your machine, use Add/Remove Programs to uninstall the Trial (Start | Settings | Control Panel | Add/Remove Programs).

2. After uninstalling the Trial, uninstall the Full version of the product.

3. After uninstalling both the Trial and the Full versions, browse to your installation directories, and delete the Trial and the Full versions' installation directories.

4. Re-install Total Access Analyzer, and visit the Updates Page to download the latest update.

5. Run Total Access Analyzer again.

If this does not resolve this issue, please contact us so that we can be of further assistance.

Total Access Analyzer 97

When I run Total Access Analyzer, I get an out of memory error, but I have plenty of memory!

There is a know issue in Access 97 that can cause out of memory errors, even when you have plenty of memory available. Check out our out of memory FAQ for details on causes and solutions for this problem.

I get error 2450, "Microsoft Access can't find the form 'TAA_Reports' referred to in a macro expression or Visual Basic code."

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.

I get error 2188, "The object you attempted to load from text has an invalid value for the property 'Top' on a rectangle."

The resolution to this is to locate the form that this error occurs on, and move the controls away from the top left edges of the form or section. This is rare, but it can be that the Microsoft Access code that is storing the information of where the controls are located is storing a negative number for the location of a control.

The resolution to this error is fairly easy to implement:

1. Locate the form that this error is occurring on in your database. The form will either have one control that spans the length of the form or several controls that are at the top most, and possibly the left most area of a specific section on the form.

2. Move all the controls 1/8th of an inch (approximate is fine) to the right and down.

3. Compile and save all modules and re-run Total Access Analyzer.

I am getting an error:  The Add-In cannot be installed because it is missing a UsysRegInfo table.

This issue can occur if you have attempted to install Total Access Analyzer using the Microsoft Access Add-in Manager. Total Access Analyzer is designed to be installed by using the stand-alone setup file.  In order to install this product, please perform the following steps:

1. Click the setup file "setup.exe".
2. Follow the prompts of the setup routine.  Enter your key number when prompted (retail version only).

If you are using the trial version Total Access Analyzer, you can launch the product from the Windows Start Menu path:

START | Programs | FMS | Total Access Analyzer | Total Access Analyzer Demo

If you are using the retail version of Total Access Analyzer, you can launch the product with the following steps:

1.         Launch Microsoft Access.
2.         Open a database or create a new database.
3.         Click Tools --> Add-Ins --> Total Access Analyzer.   

Total Access Analyzer will then display the main menu.

Please remember that each version of Total Access Analyzer is Microsoft Access version specific and is not supported for use in other versions of MS Access.  FMS offers separate versions of Total Access Analyzer for Microsoft Access 97, 2000, 2002, and 2003.

Back to Technical Support FAQ Page