ISO an independent consultant who can do a back-end repair on Sage 50 Canadian, version 2016.3

SOLVED

I hired a new bookkeeper a few years ago, and had to upgrade my version of Sage so she could work on it.  

We didn't realize until the year end that there were issues with the data.  It looks like these happened with the upgrade - likely because it was done over Dropbox.  See log below:

# HISTORICAL DATA PROBLEM: This historical table exists, but is missing an entry in the simplygrouppriv table - tbgtah01 - GLView
# HISTORICAL DATA PROBLEM: This historical table exists, but is missing an entry in the simplygrouppriv table - tbgtah01 - GLEdit
# HISTORICAL DATA PROBLEM: This historical table exists, but is missing an entry in the simplygrouppriv table - tbgtah01 - SystemAdmin
# HISTORICAL DATA PROBLEM: This historical table exists, but is missing an entry in the simplygrouppriv table - tpjbfh01 - ProjView
# HISTORICAL DATA PROBLEM: This historical table exists, but is missing an entry in the simplygrouppriv table - tpjbfh01 - ProjEdit
# HISTORICAL DATA PROBLEM: This historical table exists, but is missing an entry in the simplygrouppriv table - tpjbfh01 - SystemAdmin
# HISTORICAL DATA PROBLEM: The number of tables in the datadict for financial history is not in sync with tCompOth.nActHistSt or not in sync with the number of entries in tActHDat
# HISTORICAL DATA PROBLEM: This historical table exists, but tCompOth.nActHistSt is 6 - tJEH07
# HISTORICAL DATA PROBLEM: This historical table exists, but tCompOth.nActHistSt is 6 - tJEPHH07
# HISTORICAL DATA PROBLEM: The number of entries in the simplygrouppriv table do not match tCompOth.nActHistSt or there are entries for that table that exceed tCompOth.nActHistSt - tGMscH
# HISTORICAL DATA PROBLEM: The number of entries in the simplygrouppriv table do not match tCompOth.nActHistSt or there are entries for that table that exceed tCompOth.nActHistSt - tJEAH
# HISTORICAL DATA PROBLEM: The number of entries in the simplygrouppriv table do not match tCompOth.nActHistSt or there are entries for that table that exceed tCompOth.nActHistSt - tJEH
# HISTORICAL DATA PROBLEM: The number of entries in the simplygrouppriv table do not match tCompOth.nActHistSt or there are entries for that table that exceed tCompOth.nActHistSt - tJEPH
# HISTORICAL DATA PROBLEM: The number of entries in the simplygrouppriv table do not match tCompOth.nActHistSt or there are entries for that table that exceed tCompOth.nActHistSt - tJEPHH
# HISTORICAL DATA PROBLEM: The number of entries in the simplygrouppriv table do not match tCompOth.nActHistSt or there are entries for that table that exceed tCompOth.nActHistSt - tJETH
# HISTORICAL DATA PROBLEM: Journal entries in this historical table are outside the fiscal start or end date - tJEH02
# HISTORICAL DATA PROBLEM: Journal entries in this historical table are outside the fiscal start or end date - tJEH03
# HISTORICAL DATA PROBLEM: Journal entries in this historical table are outside the fiscal start or end date - tJEH04
# HISTORICAL DATA PROBLEM: Journal entries in this historical table are outside the fiscal start or end date - tJEH05
# HISTORICAL DATA PROBLEM: Journal entries in this historical table are outside the fiscal start or end date - tJEH06

I work in this industry, and understand what has to be done to fix the problems.  However, my daughter is critically ill so I don't have the time (or the software) to do the fix it myself ATM.

For the first two years, I was able to close the year and move on by utilizing a few tricks.  However, as of this year, I can no longer run the year end close.  I did try to remove historical data in hopes of removing the issue.  While this did remove some of the errors, it won't let me remove the data for the year with the issue.  Therefore, I'm no further ahead.

I have contacted Sage, and they will not do the repair unless I upgrade.  I'm not willing to do that so they suggested reaching out on this forum.  

Please reach out to me if you are an external consultant who can fix this issue.  Many thanks!