Duplicate U_IDs

The U_ID fields in the databases are program-generated unique identifiers that the user normally does not see. They are important for linking records and synchronizing databases.

Normal usage of Abacus ensures that these are unique, but if users have copied files or restored partial backups or otherwise accessed the databases outside of Abacus, it is possible for errors to occur.

To verify that the U_IDs are correct, select File > Synchronize > Test Database Integrity.

This test walks through all databases and checks for empty or duplicate U_IDs. (Depending on the size of your databases, it could take as long as the Pack procedure.)

When finished, the test shows a list of any records in your system that may need your attention. If these errors occur, it is a very serious condition that you must fix for the program to function.

How to View U_IDs

In the Browse windows for names or matters, you can scroll to the right to see more columns. One of these will show the U_ID field because this is an indexed field. Click the column header to sort by this field, then click Home to go to the top of the list where any blank U_IDs will be.

Or, at the Name or Matter window, click the Index button and select U_ID to sort. The U_ID field will appear for each record at the top of the window next to the Previous/Next arrow buttons.

How to Fix Blank U_IDs

If records are listed that have BLANK U_IDs, there was probably an import done that had errors, or perhaps an external program was used to add records to the Abacus database.

Abacus does NOT recommend that any external program create records in your database. Do so at your own risk. It is critical that such a program generate unique U_IDs correctly, but there are also other dangerous issues.

If there are many records with blank U_IDs, we recommend that you delete them or restore a good back up, and then add them back to Abacus correctly. If there are only a few, you can simply edit the record and make a minor change to any field. When Law saves a record and sees a blank U_ID, it generates one automatically.

How to Fix Duplicate U_IDs

If you have a long list of Duplicate U_IDs, you should try to restore a good backup and start from there. Duplicate U_IDs can difficult to handle. If there are no linked records involved (e.g. two name records with the same U_ID but no linked matters, events, docs, etc., you can clone one of the records to create a copy that will be given a new U_ID, then delete the one that was cloned.

Since the U_ID is used to control links to other databases, the same linked records will appear linked to both problem records. Be CAREFUL! If you delete one of the problem records, all the linked events and notes will be deleted! It is best to handle this by using an external database utility to edit the database. Locate the problem record and clear the U_ID field. Next, edit that record in Law and a new U_ID will be created. This record will have no linked records. If any records linked to the other problem record belong to this one, you will need to edit each of those and link them again.

Remember that this is an extremely rare condition that cannot occur through normal usage. But should it occur, the most important step is to identify the cause (external program, etc.) to keep from corrupting more records.

Contact Abacus Customer Support if you need help dealing with such conditions.