New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transactions are empty on 29.02.2016 (Leap Year Bug) #741

Closed
enasalitis opened this Issue Mar 1, 2016 · 3 comments

Comments

Projects
None yet
4 participants
@enasalitis

enasalitis commented Mar 1, 2016

BUG seems to affect all mmex versions in Windows

You can find a detailed desciption of the problem to the following Support Forum Threads:
http://forum.moneymanagerex.org/viewtopic.php?f=23&t=6394
http://forum.moneymanagerex.org/viewtopic.php?f=23&t=6398
http://forum.moneymanagerex.org/viewtopic.php?f=23&t=6392
http://forum.moneymanagerex.org/viewtopic.php?f=23&t=6399

Copying from the first forum:
"Mon Feb 29, 2016 12:45 am
As on this morning, when I opened MMEX, I do not see any of my transactions. However, the Account Balance, Reconciled Balance and Diff were showing some values.

So I clicked on Transaction filter and checked the Account name and selected the account I was looking for. All the transactions are now visible.
I have not updated MMEX. Version 1.1.1 is my version that I am using.

Closed and opened MMEX to see if that helped and still same issue.

What seems to be the problem? Please help. "

Thank you

@vomikan

This comment has been minimized.

Contributor

vomikan commented Mar 1, 2016

Leap Year Bug

If you used MMEX today (Feb 29 - leap year) you've probably noticed all your transactions are not displaying properly. All the data in the database is safe, it is only an issue with displaying items on the screen. Everything will return to normal tomorrow. You can also reset the date on your computer to yesterday and everything should reappear. Sorry for the inconvenience and thanks for using MMEX!

@mj1856

This comment has been minimized.

mj1856 commented Mar 3, 2016

According to issue 837 on SourceForge there are still issues.

(Why two bug trackers anyway? 😕 )

@vomikan

This comment has been minimized.

Contributor

vomikan commented Mar 6, 2016

screenshot 37
I can't reproduce this issue

@vomikan vomikan closed this Mar 7, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment