Balance error after only one transaction!!

[romad]

I was able to reproduce your problem - sort of.

1. Highlight last transaction and note balance.
2. Toggle sort arrow
3. Look at balance of highlighted transaction. It is different.

HOWEVER, in my test the transaction that was highlighted after the toggle was the one that had been highlighted previously BUT it had been moved down one space so the balance was different.
So if I have 10 transactions sorted ascending with #10 highlighted:

1
2
3
4
5
6
7
8
9
10 highlighted

and I toggle the sort to descending, I end up with:

9
10 highlighted
8
7
6
5
4
3
2
1

[freduruncle]

I appreciate your tenacity in trying to track this down. I'll look at what you did tomorrow but my situation is a little different I think.

To use your study, look at transaction 1. It has an entry and a balance who's absolute value equals the entry for the first entry in an account by definition. Toggle the order. Transaction 1. moves to the bottom. It has the same entry but a different balance! I'm not looking at the last transaction in a series but the FIRST! That balance should always equal +/- that first transaction entry regardless of the toggle position and for me it just doesn't. It DOES in iOS.

[romad]

Mine is always the same for the initial transaction in any of my accounts. Here is an example from the account I use to test settings and problems like yours:

Ascending.JPEG (197.72 KiB) Viewed 323 times

Descending.JPEG (201.19 KiB) Viewed 323 times

[freduruncle]

Yep, yours looks just like it does for me on the ios version. However, in PMD (in some accounts- in my case a credit card acct and a checking account) your 11/3 initial transaction would read $100 balance when its toggled to the top but when you flip it to the bottom, the $100 balance changes to $192.01! So, I'm talking about the balance shown for the oldest transaction at the bottom vs at the top.

I can't explain this. It just changes the number.....in PMD only...using the same .sql file either opened from the computer or sync'd. Doesn't matter how I get it into PMD...same result. This is under OSX and using the latest version of PMD that's available from the app store.

[romad]

Yes, that is weird! I checked all of my accounts and they all worked just like the Test account.

Have you done a search for a $92.01 transaction (if that is the actual difference you're seeing in your accounts)? Possibly a Repeating/Scheduled Transaction is being toggled?

[freduruncle]

Yes, I did that search and found two charges for that amount a couple years ago all in the middle of the transaction list. It may have even once been a recurring transaction since it was a repeating bill for a couple months. But, because of all the problems syncing recurring transactions between iOS devices, I deleted all of them before starting work with PMD. So, I have none defined on any of the 3 devices now nor did I try and sync any to te Mac at any time.

[romad]

Try this:

One at a time, delete each of those 2 transactions then manually re-enter them with the correct dates and the Cleared box checked. Perhaps something in one of those transactions is triggering the balance change.

[freduruncle]

Did that already. No change. The bias amount just returns as it was before the deletion.

[freduruncle]

Also tried adding a $0.00 transaction as the oldest date. When you do, the balance on that line goes to 92.01!

[romad]

There has to be some old transaction data hanging around in the database that is only triggered by changing the sort. IIRC, you are the first one to mention this type problem in the 20 months that PMD has been out which is why I'm not convinced it is a widespread "bug" or even a bug at all. But, unfortunately, that doesn't help you setup PMD the way you desire. Sorry, but I'm fresh out of ideas right now.

[freduruncle]

No problem. Works fine if I sort the right way. . I guess I'd still gave to call it a bug since the iOS version reads the database just fine. While I agree that there must be something funky in the database, it would still be fine if PMD handled the file the same way the iOS version does. I'm surprised it's not te same code.

[romad]

It might be because PMD comes in 3 flavors and they probably share a lot of code, particularly between the Mac OS X and Linux flavors. Also, iOS and Mac OS X, while sharing a lot, still are different systems.

[peterboliver]

Create new database on PMD. Sync your info over to it. See if this clears up the issue.

-Peter

[romad]

Peter, he already tried that based on my suggestion in post # 3; it didn't seem to fix it.

[freduruncle]

I have no idea why the problem existed but I exported all the transactions in the problematic account, deleted the account and remimported them and things now match what the ios version says. Still some sort of bug I think but at least there is a fairly simple work around....