https://bugs.kde.org/show_bug.cgi?id=434376
Jack <ostrof...@users.sourceforge.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|ostroffjh@users.sourceforge |
|.net |
--- Comment #17 from Jack <ostrof...@users.sourceforge.net> ---
I agree something has gone wrong. My suggestion to check the date filter was
in case a transaction was created with an EXTREMELY early date. (My filter is
1900-01-01.) However, you are right that any transaction with a date prior the
the account opening date would be caught by the regular consistency check.
If you save your "fixed" file back to the sql back end, does the error come
back?
Also, just out of curiosity, if you open the "bad" sql dataset, and save it to
a new MySql database, does it still show the problem. While I still don't have
any idea where the actual problem might be, answers to those questions might
provide suggestions where to look.
--
You are receiving this mail because:
You are watching all bug changes.
