Dupe Checking/Multiple Databases screen
If you have multiple ComQuest databases (in various folders), you may at some point want to create a master record of any duplicate records that are in two or more of these databases.
Only run this procedure if you truly have multiple databases; not if you are merely testing for multiple stations from the same database
In order to locate any possible duplicate records across multiple databases, you must first merge the data from those multiple databases into one common temporary database. That is the function of this procedure. One at a time, use this procedure to navigate to each of the folders on your Fileserver's hard drive that contains a valid Respondent data file (RESPONDE.DAT). When you click the lookup button to the right of the Path to add field, you must locate and specify only those folders that contain a valid RESPONDE.DAT file.
After you've located each of them, click the Add Database button, and the pertinent respondent information from that RESPONDE.DAT file will be appended to your temporary file. The record counter at the top of the screen will indicate how many respondents have been added from each database.
After you have merged all desired databases together, into one temporary database, click the Check For Dupes button. The procedure will sort through all the records in this temporary database, and any respondent records with the same phone number listed two or more times will be flagged. From the report that is generated, you will then have to delete or terminate the respondent record(s) from the database(s) you desire manually.
No changes are made to the actual Respondent files in any of your databases when you run this procedure.
The result of this procedure is merely to locate and report to you the existence of any of the same respondents (based on telephone number) in two or more of your multiple databases.
After you've completed a session of checking for duplicates across multiple databases, click the Purge Merged Database button, to empty the temporary file. Again, purging this temporary database will have absolutely no effect on your existing Respondent files, it merely empties the temporary file, so that you can create a new merged database at some point in the future.