Auto Update Information On Forms

[Netcheetar]

Hi Guys, this is my first question i have posted on here, so if i ask silly
questions that you may of already answered in the past and that i have not
noticed, please find it in you hearts to forgive me lol and just point me in
the right direction.

Hopefully this should not get you guys in here thinking too hard, i think
this ones hard but you guys might find this simple, i have had my head in my
hands trying to figure this one out for about three weeks now. I have read
all the training courses on access 2003 and i understand them quiet well, but
this has certainly got me baffled.

O.K here goes, what i am attempting to do is build a form where you can fill
out various bits of information, lets say a 'customers order form' were you
can log what a customer has ordered into it. Now i already have information
on customers like name, addresses and other bits and peices (personal
information) stored in a table called 'Customer Info'. But on the customers
order form you have to fill out the customers title, forename, surname etc.
But i would like to make it easier by entering one value (say a customer
IDCODE) and all that information being instantly entered for you (dragin the
required info from the 'customer info' table) all of this needs to display on
the same form. This would make filling in a form alot easier to fill out and
would save time repeating the same process of entering the same data over and
over, when it's already stored else were.

Now i am not sure how to approach this, but i have tried a few different
methods and shamefully failed at them all. Please someone help me out of this
prediciment. I will be absoloutley thankful to anyone who can help.

Here's a pre-thanks to anyone who attempts to help me.

Cheers all

 

[Jeff]

Hi Netcheetar

Add a subform to the mainform and set the master and child links to the
ref field which is in the mainform.

This wil pull the info from the table and show it in the subform, based
on the ref no in the mainform.

Hope this helps.

Jeff

 

[Vincent Johns]

Hi Netcheetar

Add a subform to the mainform and set the master and child links to the
ref field which is in the mainform.

This wil pull the info from the table and show it in the subform, based
on the ref no in the mainform.

Hope this helps.

Jeff

And to keep things simple, I suggest having your underlying Tables
organized the same way. For example, in the main Form, all the fields
could be in the [Customer Info] Table, and in the subform, all the
fields could come from the [Customers order] Table. You could define
one field in [Customer Info] as the unique primary key to be used
elsewhere to refer to a customer; you suggested calling that [IDCODE],
but I think it's clearer if you give it a name like [Customer InfoID] to
show what Table it belongs to. In any case, the same value you can
attach (and we'd call it a "foreign key" there, but it's the same
number) to each record in [Customers order] to show who placed the
order. Display or edit [Customers order] fields using the subform, as
Jeff suggested. The linking key must unique in [Customer Info] but
doesn't have to be in [Customers order], as several orders, we hope,
might be placed by the same customer.

Netcheetar wrote: [...]

O.K here goes, what i am attempting to do is build a form where you can fill
out various bits of information, lets say a 'customers order form' were you
can log what a customer has ordered into it. Now i already have information
on customers like name, addresses and other bits and peices (personal
information) stored in a table called 'Customer Info'. But on the customers
order form you have to fill out the customers title, forename, surname etc.
But i would like to make it easier by entering one value (say a customer
IDCODE) and all that information being instantly entered for you (dragin the
required info from the 'customer info' table) all of this needs to display on
the same form. This would make filling in a form alot easier to fill out and
would save time repeating the same process of entering the same data over and
over, when it's already stored else were.

[...]