Check Book Registry Table Design

hooks

Registered User.
Local time
Yesterday, 18:46
Joined
Aug 13, 2004
Messages
160
Hi all, Im updating my current checkbook registry database. Just want to be sure that table look ok to everyone before starting the coding process. This will be a multi user - multi account program. I have attached the relations diagram.
Please give me some suggestions as to what fields i might need to add.

Also check to relations.

Thanks a bunch.
 

Attachments

  • Relations.jpg
    Relations.jpg
    86 KB · Views: 235
1. The relationship between accounts and payees is wrong. Accounts should be related to transactions so you know which account a check was written on. They should not be related to payees. You should be able to write a check to a payee from any account.
2. Date is a poor choice for a column name since it is the name of a function. You will have problems with this if you need to write VBA.
3. It is good practice for foreign keys to be the same name as the primary keys to which they refer whenever possible. Since there are no self-referencing tables in your structure, there is no reason for the foreign key fields to have names different from the primary key to which they refer. This is especially bad in the case of the payee category table and the transaction type table since the foreign key field names are the name of a non-key field in the tables they point to.
4. I don't understand why payee category is related to the accunt name table AND the payee table.
 
Thanks Pat.

Thanks for pointing out the Date field problem. I haven't got into field names yet Im just trying to get the basic table layout figured out.

The problem im having is that multiple users will be using the database so i need a way to keep all of the Payees, PayeeDetails and PayeeCategories seperate for each user. I thought using the account would be the best way.

Say Lisa has a checking account and Cheryl has a checking account. I don't want them to see each others payees etc.

Hope this makes sense. Do you have a better way of achieving this?

Thanks Hooks
 
I guess I don't understand the purpose of this database. Are these personal accounts? Why wouldn't you give each person a separate database? If this is a business process, why are the payees secret?

If you want to assign a payee to a particular user, do it by adding UserID to the payee table and creating that relationship. Your existing setup shows that accounts are shared by users so that won't restrict a payee to a particular user. It will restrict them to a particular account which is not the same thing.
 
Let me rethink what im doing and ill post an update.

thanks Pat
 

Users who are viewing this thread

Back
Top Bottom