Unbound Form or Holding Table for Payment Section

[Jonas]

I am making a section in a program that requires input of payment
information. I have already set up a payments table. I want the user
to input the payment information for one payment, click a button and
have the information be transferred to the payments table.

Is it better to:
1. set up an ubound form for the information and move the information
to the payments table after the button is clicked?

2. have a table to hold the payment information temporarily until the
the user clicks on the button and move the information from the
holding table to the payments table at that time?

I'm pretty certain that I can get either way to work but I don't have
the foresight to know why either method would be preferred.

 

[Jeff Boyce]

Why? That is, what business need are you attempting to solve?

If you merely need to know which records are "confirmed" and which are
"pending", you could do this with a bound form and a single table. Just add
a field in the table that holds a yes/no value ... [Confirmed].

Then bind your form to that table (better still, to a query against that
table), and on the button click, "check" the [Confirmed] field.

Good luck!

--

Regards

Jeff Boyce
Microsoft Access MVP

Disclaimer: This author may have received products and services mentioned in
this post. Mention and/or description of a product or service herein does
not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.