Listbox to Populate Multiple Text Boxes

[Pisteuo]

Is there a way to create multiple control sources for list boxes?

I would like data from two listbox columns to populate two textboxes of the same record.

I know populating the secondary textbox can be accomplished through a query based on the primary listbox column. However simply passing the pair of data would work much better for me.

Thank you.

 

[boblarson]

I hope you aren't putting in data into Bound text boxes as that would violate rules of normalization. If the listbox items are able to have data that is identifiable from the selection made then that data does not need to be stored. Just the ID of the item selected in the listbox would be stored and the text boxes can DISPLAY the extra data by setting their control sources to

=[ListBoxNameHere].[Column](x)

where x is the zero-based column number of the data you want to display (so if the data you want is in column 2, x would be 1)

 

[Pisteuo]

The primary data is being passed to a bound text box. I need the secondary data to be bound as well and not only displayed.

The unique key is only being used for the listbox. I am dropping that unique key and will be using the "primary data" as the key going forward in the query process. However the "secondary data" depends on the unique key that is being dropped (this unique key is more detailed than the "primary data").

The user will be inputting two types of similar data sets that can both depend on the "primary data". The only exception being this "secondary" data that is associated with the one data set only. I would like to have 1 user form, 1 table, and simple queries, rather than parallel data sets for just one field.

Thanks again!

 

[boblarson]

The primary data is being passed to a bound text box. I need the secondary data to be bound as well and not only displayed.

Bad data design....period.

The unique key is only being used for the listbox. I am dropping that unique key and will be using the "primary data" as the key going forward in the query process. However the "secondary data" depends on the unique key that is being dropped (this unique key is more detailed than the "primary data").

did I say bad design? If not, bad data design...

The user will be inputting two types of similar data sets that can both depend on the "primary data". The only exception being this "secondary" data that is associated with the one data set only. I would like to have 1 user form, 1 table, and simple queries, rather than parallel data sets for just one field.

A specific example might help sway my opinion, but so far it doesn't look good. I think an upload of your table structure might be in order.

 

[Pisteuo]

The listbox is provided only as a reference so that the user does not have to type the data. The user will end up manually typing the secondary data anyways.

On the other hand I understand why Access would not encourage passing rogue data like I am trying to do.

Do you think the design is bad because:

1) I am not basing the dataset on the most detailed key available?
2) I am mixing two datasets (though very similar)?
3) Or because I am trying to pass rogue data?

Thanks.