![]() |
![]() |
|
If the Displaying database integrity check results page shows the message: "No integrity issues were found", then your database does not have any integrity errors and you can upgrade to PayGlobal 1.95.
If the Displaying database integrity check results page shows messages, such as: "Found x general integrity issues" or "Found x tables with integrity issues", then you must fix these errors before you upgrade to PayGlobal 1.95.
Note: Errors that the Integrity Checker finds in your PayGlobal 1.94 database will not prevent you from processing your pay successfully. However, you will not be able to process a pay successfully in PayGlobal 1.95 until these errors are corrected.
To view more information about the errors, click the View audit log button.
The audit log shows which tables and records have problems, which rules were violated, and the errors that were corrected. The audit log is saved in the selected company's Log folder and has the prefix "Database_Integrity_Check".
This section shows examples of errors and how to correct them.
You should always try to correct integrity errors logged on to the PayGlobal database, not using SQL Server Management Studio.
Blank codes
If you get an error with blank codes (as shown in the image below), then the problem is that the code does not have a value.
In this example, you need to select a valid PTDCode or NULL.

|
|
Topic: 22431