I pointed out earlier that you can be more flexible with the design now and it will save you from having to make changes later. I've developed a lot of applications. I have a very good sense of what things are actually cast in concrete and unlikely to change and what things are likely to change. Think of this as defensive driving. You don't hit the car that cut you off because he was wrong. You avoid him and maybe make an obscene gesture. When you are on the highway, you don't want to be trapped without an escape plan. This is the same thing. Do you have more than one bank account? I do. I have one personal checking account, one for the household, and another for my business. They happen to be at the same bank but my other accounts are at different banks. To make an assumption this early in the design that no one would ever have more than one account is very shortsighted.
One of my good friends didn't like the way her husband balanced the checkbook so she kept the master and gave him a "sub" ledger. She would "transfer" spending money to "his" account. It was all one account. You are not actually doing the transfers. You are just tracking them so you can make the child's account number 123456-sub and the parent's 123456 if you want to.
As long as the type of transaction is stored, you can report whatever you want. Add a Category field so you can distinguish Expenses from Withdrawals. Add a description field so you know the expense was for milk.
Regardless, you need the "to" fields in the tables so you know to whom the money went. All you have right now is who sent it (MemberID)
If you have a better Idea ! can you edit or give a demo.
I told you what I thought the schema should look like. You made some changes.
I can modify the tables but I'm not messing with the forms. I don't know why your forms are popup and model and open to a "new" record. How do you look at existing data? There is NO reason to have code in the load event that goes to a new record. There is a form property for that so you can open the form to view or to add. That allows you to use a single form for BOTH adding and editing. You do not want to put yourself in the position of having to manage the same validation code on two versions of a form and that is what will happen once you realize that validation is required in order to avoid bad data.
Is this a task you've set for yourself to learn how to create a database? Or, is this something you really need. Here is an Austrailinn company that offers a "free" version. I am always leary of "free" stuff since no one develops software to give away for free. If the software is "free", YOU are the product but it looks like they also have paid versions. Using a product like this, you would need to equate "members" with checking accounts since the product is for a single person.
Free Personal Finance Software. Download Includes Easy Checkbook Register (nchsoftware.com)
Take a look at this software and see if it makes sense to you.
