|
|
|
"I want to praise your support staff for being very helpful and friendly. Technical support was extremely helpful and gave me much more information than your average support person ever does. Thank you. " - Nora L. |
|
|
|
|
Microsoft
Access Resource Center
Total Access Detective
Frequently Asked Technical Support
Questions
All Versions
Total Access Detective 2000
Total Access Detective 97
When I run Total Access Detective 97, I get an out of memory error, but I have plenty of memory!
I get error Error 3258, "Ambiguous outer joins" when I run Total Access Detective.
I get error Error 3239, "Too Many Active Users" when I run Total Access Detective.
All Versions
What version of Total Access Detective do I need? What versions of Access does Total Access Detective support?
Total Access Detective is an Access add-in, and is Access version specific. For example, Total Access Detective 2003 can only be opened through Access 2003.
However, Total Access Detective will work with databases in any format that is supported by the specific version of Access. For example, Total Access Detective 2003 will work with databases that are in Access 2000 format or 2002-2003 format, provided that the database is opened in Access 2003.
The following versions of Total Access Detective are available:
- Total Access Detective 2003 is available for Access 2003.
- Total Access Detective 2002 is available for Access 2002 (XP).
- Total Access Detective 2000 is available for Access 2000.
- Total Access Detective 97 is available for Access 97.
Check the Product Compatibility Chart for version information for all of our products!
Can I try Total Access Detective before I buy it?
Although there is not a trial version for Total Access Detective, you can take the online tour to find out more about this product.
Also, remember that FMS products come with a 30-day money back guarantee, so you can buy with confidence!
When I run Total Access Detective, I get error Error -2147467259, "You do not have the necessary permissions to use the object."
Total Access Detective will detect differences in 2 Secured databases provided:
1. Both Secured Databases MUST be using the same workgroup security File (.MDW).
2. The User Group MUST
have at least Open/Run permissions on the DATABASE. Our application opens
the databases as a user but not a specific user. Thus the User Group (which
cannot be removed from individual permissions) must have at least Open/Run
permissions on the DATABASE (not necessary for specific objects, just needed
at the database level).
3. The File attributes are not set to "Read Only" (right click on the DB file as you see it in Windows Explorer, and choose Properties. Ensure 'Read Only' is not checked.)
To use Total Access Detective on a Secured Database:
1. Open one of the Secured databases using the Workgroup Security file.
2. Close the Database, BUT do NOT close MS Access. Leaving MS Access open automatically allows any database files opened in that copy of MS Access to use the same Workgroup Security file.
3. From the MS Access File menu, choose Open, and browse to the location where Total Access Detective is installed.
4. Choose the file named:
- TAD8DET.MDB (Total Access Detective 97)
- Tad9det.MDB (Total Access Detective 2000)
- tadetect.mdb (Total Access Detective 2002)
5. Run Total Access Detective as normal and select the 2 secured databases that use the Workgroup Security file you originally opened MS Access with.
Running 2 Object compare simply requires that you open your database with the Secure Workgroup File, then selecting Tools, Add-ins, Total Access Detective as normal.
Total Access Detective 97
When I run Total Access Detective 97, 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.
When I run Total Access Detective 97, I get an error that says my database is not opened exclusively (Error 3186).
Please take the following steps to ensure that your database is opened exclusively:
1. Close all Microsoft Access instances open on your machine.
2. Find all .LDB files on your machine or in the directory holding the database you want to open exclusively. Ensure that no one else is using the database, and delete these .LDB files.
3. Open Microsoft Access (DO NOT open a database or use a shortcut to open Microsoft Access).
4. Go to the File Menu, and choose Open.
5. Choose the database you want to open and ensure that the Exclusive check box is checked.
6. Click Open.
The text for my differences truncates after 255 characters!
This suggestion has been implemented in Total Access Detective 2002, which allows you to decide whether to truncate after 255 characters, or to show all differences!
Unfortunately, prior to Total Access Detective 2002, the product used a text field (max 255 characters) to store the differences in and therefore, the full data may not fit in its entirety in the field. Since we take into account that there may be differences longer than 255 characters, we must <truncate> the data in order to maintain the ability to index items on this field. Since this may occur, we still show you the record number that the differences occur in so you can find the exact differences in it.
I get error -2147319779, "Method 'FullPath' of object 'Reference' failed" when I run Total Access Detective.
We have encountered this issue in Total Access Detective 97 when there is a demo or beta of one of our products installed that has not been removed prior to installation of the full released version. To resolve this please do the following:
1. Uninstall Total Access Detective, as well as any demo of Total Access Detective.
2. Open the registry by choosing Run from the Start Menu, and typing the command line "regedit."
In the registry double click the following Path:
HKEY_LOCAL_MACHINE
3. Delete the registry entry HKEY_LOCAL_MACHINE, Software, FMS, Total Access Detective.
4. Reinstall Total Access Detective and apply any updates that may be available from our Web Site.
If these steps don't resolve the issue, please follow these steps.
1. Open your database exclusively.
2. Choose Options from the Tools menu, and on the Advanced tab, change the name of the project. This decompiles all the code in the database.
3. Open a module, and choose Debug, Compile and Save All Modules.
4. Repair and compact the database.
5. Close and re-open the database and run Total Access Detective again.
I get error Error 3258, "Ambiguous outer joins" when I run Total Access Detective.
The error you are encountering about "ambiguous outer joins" can occur when you try to run or document a query with certain combinations of joins. For further information, see the Microsoft Access 97 help menu topic "ambiguous outer joins".
For an example of what causes the conflict and information on how to resolve it, search the Microsoft Knowledge Base for article Q124937, "Explanation of 'Ambiguous outer joins' error message."
I get error Error 3239, "Too Many Active Users" when I run Total Access Detective.
It may be possible that there is interference on the Network that is not allowing your to write to it or that there are .LDB files left on your computer. Please follow these steps to resolve the issue:
1. Close all instances of Microsoft Access.
2. Search for and delete any .LDB files you can find on your computer.
3. Move or copy the Database you are using Total Access Detective on to the local drive and direct the output database local as well.
4. Rerun Total Access Detective.
Total Access Detective 2000
Our Development Team has resolved this issue in the latest update available for Total Access Detective 2000.
Updates for our products can be found online at the following URL:
http://www.fmsinc.com/free/updates/index.html
