Linking pages

[Albert]

I am creating a two-page form. In the first page we input client data and in
the second page we want to input a table to keep track of the payments done
by each client.

 

[Steve]

When you record payments, you need to know what the paymens are for and
whether the payment is payment in full for something or whether there are
multuple payments for the same thing. Payment in full for something is like
a payment for gasoline when you fill up your tank. Multuple payments for
the same thing is like monthly mortgage payments over fifteen years.

PC Datasheet
Providing Customers A Resource For Help With Access, Excel And Word
Applications
(e-mail address removed)

 

[tina]

you don't say what your *tables* structure is; you should have, at minimum,
two tables, as

tblClients
ClientID (primary key)
<other fields that describe a client, but NOTHING about payments>

tblPayments
PaymentID (primary key)
ClientID (foreign key from tblClients)
PaymentDate
<other fields that describe a single payment from a single client, but
NOTHING about the client other than the ClientID>

that's a standard one-to-many relationship: one client may make many
payments, but each payment is made by only one client.

a standard form setup would be a main form bound to tblClients, with a
subform bound to tblPayments; the mainform/subform linked on the ClientID
field in each table.

hth