How do I pass the value from a list box into a query?

[Andrew]

I've got two tables in my DB, a Client table and an Event table.
There are many events for each client. The form I designed is based
off of the Client table and the subform within it is sourced from the
Event table.

The way things are currently designed places a list of clients on the
left side of the form (with a list box), and then there's a subform on
the right side of the main form with fields to enter event
information.

What I'd like to have happen is to simply select a client name from
the left side, enter the event information on the right and click
submit, and then move on selecting other clients, etc. Right now I
have a list box
providing the client list. Is this right? I know there's an option
when using the listbox wizard that involves using a record selected in
the list box for other functions, but I can't figure out how that
works exactly.

Thanks,
Andrew

[Mal Reeve]

Andrew,
Rather than the Left side of the form, go to Design View and view the Form
Header/Footer.
If you create a combobox that gets its data from the same source as the
listbox (and use the wizard to create it) The option of "Find a record on
my form..." will be available.
While you don't need to stick with the Combobox, it will show you the
appropriate code to use.
Personally though I would use a combobox for this type of
application....especially if the client list grows to a long long list...a
lot less scrolling with the combobox.

HTH
Mal.

"Andrew" <sp****@gnt.net> wrote in message
news:d8**************************@posting.google.c om...

I've got two tables in my DB, a Client table and an Event table.
There are many events for each client. The form I designed is based
off of the Client table and the subform within it is sourced from the
Event table.

The way things are currently designed places a list of clients on the
left side of the form (with a list box), and then there's a subform on
the right side of the main form with fields to enter event
information.

What I'd like to have happen is to simply select a client name from
the left side, enter the event information on the right and click
submit, and then move on selecting other clients, etc. Right now I
have a list box
providing the client list. Is this right? I know there's an option
when using the listbox wizard that involves using a record selected in
the list box for other functions, but I can't figure out how that
works exactly.

Thanks,
Andrew

[Andrew]

Thanks for the help Mal. I'd rather use a list box if possible since
1) the client list will rarely get longer than 25 and 2) the people
using the system will have a much easier time with a list box than a
combo box (not the most computer savvy folks). If I just change the
type from a combo to a list is there anything else I'd have to take
into consideration?

Thanks,
Andrew
"Mal Reeve" <lo*****@earthlink.net> wrote in message news:<5_******************@newsread3.news.atl.eart hlink.net>...

Andrew,
Rather than the Left side of the form, go to Design View and view the Form
Header/Footer.
If you create a combobox that gets its data from the same source as the
listbox (and use the wizard to create it) The option of "Find a record on
my form..." will be available.
While you don't need to stick with the Combobox, it will show you the
appropriate code to use.
Personally though I would use a combobox for this type of
application....especially if the client list grows to a long long list...a
lot less scrolling with the combobox.

HTH
Mal.

[Mal Reeve]

I don't think anything else would need changed...

look in help for the .selected
which is what you want....
If its a simple list box (only one selection allowed)
then I think that using the value will work the same way as the code
produced by the wizard.

Mal.

"Andrew" <sp****@gnt.net> wrote in message
news:d8**************************@posting.google.c om...

Thanks for the help Mal. I'd rather use a list box if possible since
1) the client list will rarely get longer than 25 and 2) the people
using the system will have a much easier time with a list box than a
combo box (not the most computer savvy folks). If I just change the
type from a combo to a list is there anything else I'd have to take
into consideration?

Thanks,
Andrew
"Mal Reeve" <lo*****@earthlink.net> wrote in message
news:<5_******************@newsread3.news.atl.eart hlink.net>...

Andrew,
Rather than the Left side of the form, go to Design View and view the
Form
Header/Footer.
If you create a combobox that gets its data from the same source as the
listbox (and use the wizard to create it) The option of "Find a record
on
my form..." will be available.
While you don't need to stick with the Combobox, it will show you the
appropriate code to use.
Personally though I would use a combobox for this type of
application....especially if the client list grows to a long long
list...a
lot less scrolling with the combobox.

HTH
Mal.

[Mal Reeve]

Another thought...

Use a combo-box, and the code auto generated....
And use the On Open event of the form to set the combobox as dropped.

txtComboBoxClientList.Dropdown

Making it look an awful lot like a listbox...

Mal.

"Andrew" <sp****@gnt.net> wrote in message
news:d8**************************@posting.google.c om...

Thanks for the help Mal. I'd rather use a list box if possible since
1) the client list will rarely get longer than 25 and 2) the people
using the system will have a much easier time with a list box than a
combo box (not the most computer savvy folks). If I just change the
type from a combo to a list is there anything else I'd have to take
into consideration?

Thanks,
Andrew
"Mal Reeve" <lo*****@earthlink.net> wrote in message
news:<5_******************@newsread3.news.atl.eart hlink.net>...

Andrew,
Rather than the Left side of the form, go to Design View and view the
Form
Header/Footer.
If you create a combobox that gets its data from the same source as the
listbox (and use the wizard to create it) The option of "Find a record
on
my form..." will be available.
While you don't need to stick with the Combobox, it will show you the
appropriate code to use.
Personally though I would use a combobox for this type of
application....especially if the client list grows to a long long
list...a
lot less scrolling with the combobox.

HTH
Mal.

[Pieter Linden]

sp****@gnt.net (Andrew) wrote in message news:<d8**************************@posting.google. com>...

I've got two tables in my DB, a Client table and an Event table.
There are many events for each client. The form I designed is based
off of the Client table and the subform within it is sourced from the
Event table.

The way things are currently designed places a list of clients on the
left side of the form (with a list box), and then there's a subform on
the right side of the main form with fields to enter event
information.

What I'd like to have happen is to simply select a client name from
the left side, enter the event information on the right and click
submit, and then move on selecting other clients, etc. Right now I
have a list box
providing the client list. Is this right? I know there's an option
when using the listbox wizard that involves using a record selected in
the list box for other functions, but I can't figure out how that
works exactly.

Thanks,
Andrew

Andrew,
are you sure you want just two tables? Can two people attend the same
event? If so, you need [Person]--[Attends]--[Event]. So Attends
would be something like (PersonID, EventID) with *both* as primary
key. Then if you wanted to have all the events a person is attending
in a listbox and move them back and forth, say between lbxAttending
and lbxNotAttending, you could use the .AddItem, and .RemoveItem
methods of the listbox (assumes 2002 or later). Then if you wanted to
use the selected items in a query, there's code right here...
(it's on www.mvps.org/access somewhere...
right here:
http://www.mvps.org/access/forms/frm0007.htm

basic format of your form
lbxUnselected (one button for add, one for remove) lbxSelected

then use the code from the link to work with your query.

HTH,
Pieter