Logical Certify and Repair
Logical Certify
A logical certify checks for errors in system logic, and creates its own repair files which correct the problem in the majority of cases. If an error is reported that indicates there may be a problem with your system logic, MYOB support may ask you to run a logical certify and repair across your database.
Follow these steps to run a logical certify:
- Take a copy of the live database, and place this on another machine (the process may take a considerable amount of time to run).
- Create an icon on the desktop (of machine with live copy) with
these properties:
C:\{path to bin}\bin\jade.exe path=C:\{path to system}\system ini=C:\{Path to the ini file}\jadegt.ini schema=RootSchema app=JadeLogicalCertifier server=SingleUser
- Click the icon to open the JADE Logical Certifier form.
- Select the option to Certify, All Schemas and specify a directory for the certify log file (this should be an empty directory created specifically for the log, err, and repair files).
- Click Certify/Repair to run the certify.
- When the process is complete, take a backup of the folder (created
specifically for the logical certify in previous step - in the above
example, c:\temp), and place
it in a separate directory (this is used as input to the repair
process).
Note: Greentree Desktop creates repair files if it encounters errors during the certification process.
Logical Repair
Follow the steps outlined below to run a logical certify:
- Take a backup of Greentree.
- Create a new folder in a separate directory.
- Copy the output files generated by the logical certify into the new folder.
- Create an icon on the desktop with these properties:
C:\{Path to Bin}\jade.exe path=c:\{Path to System}\system ini=c:{Path to ini}\jadegt.ini schema=RootSchema app=JadeLogicalCertifier server=SingleUser
- Activate the icon to open the JADE Logical Certifier form.
- Select the option to Repair, and in the log file directory, enter the path to the new folder created in step 2 of the repair process.
- Click Certify/Repair to run the repair.
When the process is complete, a message should indicate there are no errors. Check to see if the original problem is corrected. If it has, then take a backup of the live system, and apply the repair files to the live system, following the steps outlined above. The database must remain closed while this process is being run.