Reloaded Adagio Ledger 9.0D onto a new computer but the data integrity check throws out an error "account is missing 8.0 compatible record " for each account. The rebuild didnt solve the problem either. As a side note at the end of the install the following warning also appeared: Renamed files locking or rights issues:
RAK/dict/GLH00b8.TMP, GLH00bd,GLH00be,GLH00bf and GLH00c0 all.TMP
Please help

"account is missing 8.0 compatible record " is referring to GLDATA, GLDATAI and GLDATAI2.

Those files sizes should have been conserablly larger than 1000 bytes.

They are showing 920, 40 and 43 KB respectively.

Then they should be OK..

I know the Rebuild of GL9.0D (120207) adds back the GL 8.0 Data record so there must be something more to this issue.

There is a minimum charge of $400 for a database repair and a zip of the data may be uploaded to www.softrak.com/dbr

Will retry the install tonight strange that it still shows 111017 as the date where your reference shows 120207 maybe i'm missing an update.

Your version should also repair the data, 120207 was a hot fix that dealt with:

Hot Fix - Adagio Ledger 9.0D (2012-02-07)
When a batch was Unposted and the option 'Delete entries from posted?' was selected, the units were not increased/decreased by the unposting.

Ok thanks I will reinstall and see how it goes.

Did the reinstall still has the same message. Just as a bit of background I used the download information received from Softrak which first downloaded the update then asked for the original install codes etc. to continue. If this is the correct way then I am not sure why this is not working as the data files are backups that worked on the prior computer. The download did once again show warnings about locking or rights issues this time showing GLH00057 and GLH00058.TMP as well.

Point the GL at the sample data ( ..\Softrak\Ledger\Samdata ) and do a DIC. If the sample data is OK then the problem is with your data. If the problem shows up in the sample data then the problem is with the installation.

Hi Michael, it has given me the same error so must be the installation. We are using Windows 7 Pro if that matters but other than that just followed the normal download procedures.