Accounting 2.0 - Prompted Message: Error during upgrade to 2.0-Invalid Data Definition Language Statement, error message is Violation of PRIMARY KEY constraint … The duplicate key value is (CR Default): Difference between revisions
Accounting 2.0 - Prompted Message: Error during upgrade to 2.0-Invalid Data Definition Language Statement, error message is Violation of PRIMARY KEY constraint … The duplicate key value is (CR Default) (view source)
Revision as of 04:36, 30 August 2022
, 1 year agono edit summary
(Created page with "'''Question:''' When upgrade database from 1.9 to 2.0, error message prompted “Invalid Data Definition Language Statement, error message is Violation of PRMIARY KEY constraint … The duplicate key value is (CR Default). Why? File:CR default1a.png After clicking OK, another message prompted. File:CR default2.png <u><b>Possible Reason:</b></u> This is due to the “CR Default” (document format name) is used in version 1.9, and in AutoCount 2.0 there is...") |
No edit summary |
||
Line 1:
'''Question:''' When upgrade database from 1.9 to 2.0, error message prompted “Invalid Data Definition Language Statement, error message is Violation of PRMIARY KEY constraint … The duplicate key value is (CR Default). Why?
[[File:CR default1a.png|1000px]]
| |||
