Hammer wrote on Feb 25
th, 2009 at 5:27pm:
I'm not sure what you read, but you should use multiple databases for multiple kinds of data.
Hammer,
it was an old post from 2005 (see below). It seemed unusual, but 'don't ask, don't learn!'.
Re: UserSelect Question
Reply #55 - Apr 1st, 2005, 12:55pm Quote Quote
I hope this helps explains my query.
I have only 1 database named [newdispatch.db] it has many forms. My main form is called [dispatch] it has a most excellent lookup (thanks to all of you) of the customers names and fills in the customers address, phone and other info from the [CUST] form.
The [dispatch] form also has fields named (Machine Type) (Model) and (Serial).
I have a userselect menu in the (Machine Type) field that looks up in the [Equipment list] subform of the [CUST] form and pulls up all of the equipment of that customer. That works exactly as desired and looks like this
If @in (Machine Type, "..") > 0 then
Machine type = @Popupmenu (@xlookupall("Data\newdispatch.db", Company Name, "equipment list!co_Name", "Equipment type"), "equipment type")
I would like to be able to auto fill the (Model) and (Serial) fields on the [Dispatch] form with the info from the (Machine Type) field from the subform [Equipment List]
Many of my customers have the same type of equipment (but not the same serial number) so I cant do the xlookup (abc machine) from the (machine type) field. I would have no objections of adding a key field if need be.
This might be a better break down on my db
[Newdispatch.db]
[Dispatch] form, fields we are dealing with (Company Name), (Machine Type), (Model), and (Serial).
[CUST] form fields (Customer Name)
Natural linked to [CUST] its subform [Equipment List] subform. fields (Equipment Type), (Model No), (Serial No), (Other Info), (co-name)