Difference between revisions of "Debug Assertion"

From ISoft Wiki
Jump to navigationJump to search
(Changing categories to new convention)
(Added a bit more detail)
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
A debug assertion is a hard crash that happens when a code error is not handled correctly by the software.
A debug assertion is a hard crash that happens when a code error is not handled correctly by the software.
This could happen for any number of reasons - when you report the error to ISoft, make sure to let them know what screen was open and what you were doing at the time.


== Possible causes ==
== Possible causes ==
Line 5: Line 7:
If a crash occurs while the QBToolkit is attempting to contact Quickbooks, it is often the result of the QBSDK being a different version from what the software expects (or, it is simply not installed).
If a crash occurs while the QBToolkit is attempting to contact Quickbooks, it is often the result of the QBSDK being a different version from what the software expects (or, it is simply not installed).


[[Category:ITrack/Problems/General Problems]]
[[Category:ITrack/Problems/Error Messages]]

Latest revision as of 15:28, 14 July 2009

A debug assertion is a hard crash that happens when a code error is not handled correctly by the software.

This could happen for any number of reasons - when you report the error to ISoft, make sure to let them know what screen was open and what you were doing at the time.

Possible causes

QBToolkit (Pro)

If a crash occurs while the QBToolkit is attempting to contact Quickbooks, it is often the result of the QBSDK being a different version from what the software expects (or, it is simply not installed).