11-27-2012 01:49 AM
I have tried several combinations including Contact/phone and contact/address1/phone.
i have successfully scanned for dups many times in the past with this database without problems. The only difference this time is that I just moved the database to a new computer.
i suspect some sort of problem. I did do a repair on the database, but it didn't help.
11-27-2012 08:10 AM
Try a field that you know to have duplicates (like the state field) and nothing else. Does that work? Try the demo database also.. that will help you to know if it's a training issue (user), installation of the program, or the database itself.
11-27-2012 08:20 AM
When you use multiple fields for the duplicate scan, all must fields must match exactly. The aST! duplicate scan doesn't have the capabilities for a fuzzy search.
11-27-2012 08:32 AM
I didn't have a demo, but I created a new test database with mostly duplicate records. The Scan for Duplicates identified them correctly.
Also, the database in question is remotely synced with two other databases that contain the same information (of course). The Scan for Duplicates routine is not identifying the duplicates I know exist on any of the three essentially equal databases.
Finally, on the database in question, I manually made two new records using the exact same procedure I used to make duplicate records in the test database I created. The Scan for Duplicates procedure failed to identify the new contacts as duplicates.
When I scanned for duplicates on the test database, there was a momentary pause while the system found them (in a database with 4 records). When I do the same on my regular database with 2400 records, the notice that no duplicates were found comes up immediately.
By the way, I found nothing in the knowledgebase about this.
11-27-2012 08:44 AM - edited 11-27-2012 09:28 AM
Here's yet another insight. Most recently, I have been accessing this issue on a remote database. However, it first occurred on the parent database. On this board, it is asserted that duplicate checking can only be done on the parent. That's not my experience. (I am running Act 2013 Pro with Hot Fix 1) However the error messages I am getting are exactly the same including the metadata issue) on both the parent and the remote. (Others have gotten that same message when trying to change the defaults through tools/preferences, but it is not stated if or how it was remedied.)
11-27-2012 09:42 AM
Basically you have proved that the problem is with your main database. Do all the maintenance repairs on that database within the ACT! program and in ACTdiag. If that doesn't fix the problem then you will need to consider having the database repair.
If you need to do frequent duplicate scans, you should consider the third party product from http://www.egenconsulting.com/egcproducts.html.
11-27-2012 01:04 PM
In the ACT! program database maintenance is on the Tools menu. In ACTdiag there are several repairs listed on the menus.