form input and output

[Guest]

I'm trying to create a form that takes information from a query then after
the user enters information in a couple of non query related fields dumps
info from the form into a new table or query

It looks like this

Query Form
Table
ID ID
ID
L. Name L. Name
F. Name F. Name
MI MI
Phone# Phone #
First callback
first callback
Second Callback
Second callback
Confirmation
Confirmation
Reference
Reference


I'm not even sure if what I'm thinking is possible. Any help here on how to
get started
Thanks

 

[John W. Vinson]

On Tue, 20 Mar 2007 12:52:08 -0700, Eric Johnson <Eric

I'm trying to create a form that takes information from a query then after
the user enters information in a couple of non query related fields dumps
info from the form into a new table or query

It looks like this

Query Form
Table
ID ID
ID
L. Name L. Name
F. Name F. Name
MI MI
Phone# Phone #
First callback
first callback
Second Callback
Second callback
Confirmation
Confirmation
Reference
Reference


I'm not even sure if what I'm thinking is possible. Any help here on how to
get started
Thanks

It's surely possible - and it's almost certainly A Very Bad Idea. Why would
you want to store *the same* data redundantly in two tables? What are you
trying to accomplish, in real-world terms?

John W. Vinson [MVP]

 

[Guest]

The only information that is common between the two tables is ID. That said
what I'm doing is taking a query with contact information pulling it up in a
form. On that form will be some blank fields for when the user was contacted
and the results of that contact. That information plus the ID would be put
in another table to be queried against other information later


I hope that makes things clear

Eric

 

[John W. Vinson]

The only information that is common between the two tables is ID. That said
what I'm doing is taking a query with contact information pulling it up in a
form. On that form will be some blank fields for when the user was contacted
and the results of that contact. That information plus the ID would be put
in another table to be queried against other information later

Hrm. It sounds to me like a decent solution would be to have a Form with the
person's information, with a Subform bound to a second table for the
information about the contact. If you use the ID as the master/child link
field, you'll be storing the contact information; I don't see what benefit you
get from *seeing* the biographical information twice as you propose.

John W. Vinson [MVP]