Rebuild Local Database – Claims Estimate™

Link to this page:

Rebuild Local Database – Claims Estimate™

The below might help to resolve some issues in Claims Estimate™.

Deleting ItemDatabase and ItemDatabaseVersion files and renaming the mClaim.db and mClaim.ini files can help to resolve some issues in particular with regards to the UI(program user interface), language, line items and other issues related to databases and also Claims Estimate™ settings.
Doing this will trigger Claims Estimate™ to re-download a fresh copy of the pricing databases associated to claims.

If you work with multiple Claims Estimate™ environments (Prod-US, Prod-CA, Staging etc.)

Remember that Claims Estimate™ is independently installed for each of these environments into different installation folder locations.

1. Log in to Claims Estimate™

2. Release ownership of all claims for ALL users you have used in Claims Estimate™ *
     - including impersonations

1. Checkmark all claims that you have ownership of in Claims Estimate™
   
   
   
2. From the My Claims menu at the top, click on the Release Ownership button.
   

*If you use multiple User Accounts, release all claims for all accounts.
The installation file mClaim.db contains data for ALL users using Claims Estimate™ in the computer. 

3. Once all claims have been released successfully, close Claims Estimate™

4. Using Windows File Explorer, go to the folder where Claims Estimate™ is installed

Typically in:

1. C:\Program Files\CoreLogic Estimate
   or
2. C:\Users\YOURUSERNAME\AppData\Local\Programs\CoreLogic Estimate)
   or
3. Right click on program icon shortcut and select "Open file location"

5. Delete all ItemDatabase files and all ItemDatabaseVersion files

6. Rename the file “mClaim.db” to “mClaim_old.db” (or any other name) 

7. Rename the file “mClaim.ini” to “mClaim_old.ini” (or any other name)

8. Start Claims Estimate™ and log in.  Synchronization will begin automatically.

Check to see if the issue you were experiencing is resolved.

.