Hi Forum!
After several attempts over the years to try and build a replacement application for the now non-supported Microsoft Money Suite of applications (they worked great and gave me almost everything I needed, but found out that it does not run on Windows 10...), I decided I should bite the bullet and sit down and get this project done, once and for all!
My Design Goal: to build an Access 2013 database / application that I can use to store transaction information for multiple bank accounts and then use that information at the end of each tax year to crunch the numbers based upon my local tax laws (Netherlands, although I see that it should be possible to load any set of tax laws being able to be loaded into the system and the system crunches based on those, but this is just a concept ). Also, to analyse spend on various categories (food, clothing household utilities, etc.)
Now, with a single bank account, I think this is relatively simple - 1 table for the actual transactions in that account and other tables for the other information in each transaction (categories, payees, etc.) However, I'm struggling to understand how I would approach this for multiple bank accounts. My thought is that I would still need to have just one "Transactions" table and it holds all transactions for all accounts. But then how do I handle transactions between accounts, for example? That one is giving me headaches!
I've looked through this and other forums for answers / advice on approaching this, but the answers seem to be varied depending on who you ask (of course ).
Many people say "Fool! Why bother when you can buy an off the shelf package?" True, but where's the fun in that!? My purpose is to learn by doing and I have a need for an accounts system and I think I will learn a lot by building it (and more than a little help from this forum, I'm sure! )
Can anyone point me in the right direction or show me a thread I may have missed on this topic?
Any and all help is of course very much appreciated!