Replies: 2 comments
-
Yes, I agree. The program is very lightweight so I decided not to include and over complicate the design with a dedicated database engine. I assume that most users would not have tens of thousands of trades every year, so I simply load ALL of the trades directly into memory at program startup. I added a Year End Close feature in case the load of transactions became too great and the user wanted to cull out older ones. I performed my Year End procedure yesterday for my trades. I copied the whole folder (including the TradeTracker exe) to a backup folder and renamed it "2023-archive", so if I ever need to look at my 2023 data I can easily access it. In the current year folder, I ran TradeTracker and performed the Year End procedure removing all CLOSED trades from Dec 31, 2023, or earlier. I will think about this more. I do like the idea of expanding the Closed Trades filters to be more like the Transactions filters. |
Beta Was this translation helpful? Give feedback.
-
Maybe a tag system makes sense in this context. You can give the trades 1-x tags when creating them and then include these tags in the filter criteria. The categories go in a similar direction, but you have to choose one. I can assign countless tags for a trade. Possibly also a full test search for searching in comments and notes. I have used this so far at Stonkjournal.com. |
Beta Was this translation helpful? Give feedback.
-
I don't think it is necessary to delete old years. You could keep the old trades and use a filter to select the period under Closed Trades, as was already done under Transactions. If statistics or charts are added later, then you can analyze your time periods.
Beta Was this translation helpful? Give feedback.
All reactions