J
Jan Il
Hi all - Access 2002 XP - Windows ME
I am trying to set up a checking account registry db. At the moment I have
tree tables, but, not sure if this is really the right way. Perhaps I only
need one table to do what I need.
Table No. 1 consists of:
CheckID (PK) - Autonumber)
CheckNo
ActionDate
TransactionDesc
CheckAmt
DepositAmt
Table No. 2 consists of:
AccountID (PK - Autonumber)
CheckNo
AccountType (money paid to, or income received from)
They are set to a one-to-many relationship. A query is to calculate the
current balance to display in the related form, and ultimate report.
I am not sure if this is the right structure, or, since the information is
not that extensive, if it should be put into one table. The db will only be
tracking the checking account records. Money in, money out, paid to, what
for, and what the current balance is. I looked for a template or existing
setup for this, but, all I found were 'way' too extensive for what I need to
do.
I have a data entry form to record the information, and one to filter the
information by specific dates will be created. But, while things are still
in the setup stage, I wanted to just double check if I am on the right path
here or not. I am not sure if I need a select or update query, so, how I set
up the tables may influence that part too.
I would truly appreciate any information or suggestions. This is my first
attempt at this type of function, so, I don't now just how many tables I
need to get the right results and tracking.
Best regards,
Jan
I am trying to set up a checking account registry db. At the moment I have
tree tables, but, not sure if this is really the right way. Perhaps I only
need one table to do what I need.
Table No. 1 consists of:
CheckID (PK) - Autonumber)
CheckNo
ActionDate
TransactionDesc
CheckAmt
DepositAmt
Table No. 2 consists of:
AccountID (PK - Autonumber)
CheckNo
AccountType (money paid to, or income received from)
They are set to a one-to-many relationship. A query is to calculate the
current balance to display in the related form, and ultimate report.
I am not sure if this is the right structure, or, since the information is
not that extensive, if it should be put into one table. The db will only be
tracking the checking account records. Money in, money out, paid to, what
for, and what the current balance is. I looked for a template or existing
setup for this, but, all I found were 'way' too extensive for what I need to
do.
I have a data entry form to record the information, and one to filter the
information by specific dates will be created. But, while things are still
in the setup stage, I wanted to just double check if I am on the right path
here or not. I am not sure if I need a select or update query, so, how I set
up the tables may influence that part too.
I would truly appreciate any information or suggestions. This is my first
attempt at this type of function, so, I don't now just how many tables I
need to get the right results and tracking.
Best regards,
Jan