I think John's right: it would be better as 2 tables. What the person should
pay, and what they actually pay don't always match.

You will need to consider what possibilities you need to design for, e.g.:
- a person makes multiple payments on one policy (e.g. when struggling
financially)
- a person makes a single payment that covers multiple policies (e.g. one
check covering a guy and his wife.)
- a person prepays his policy (e.g. one check covers the next 3 payments
due, because he will be away.)
- a payment is partly check and partly cash (or card.)
and the really curly one:
- you need to receipt a payment for a policy that has not been created yet.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"John W. Vinson" wrote in message
...
On Fri, 4 Apr 2008 12:16:18 -0700, Mykas_Robi
wrote:

I will check back later on and submit my new table design. Based on the
information you proved I can probably have the accounts receivable and tax
info tables in one table.

You should consider this carefully. Those sound like two different kinds
of
data, which should be in two many-side tables related to the accounts
table.
--

John W. Vinson [MVP]