Retaining Information from Related Unbound Combo Boxes

[Steven19]

I presently need advice:

I presently have a table:
Has a Primary Key, Then Field 1, Field 2 an Field 3, Field 4.

I have an unbound form that has 3 combo Boxes (unbound).
Combo Box 1, contains Field 1, after update Combo box 2 is updated, and shows the filtered list of Field 2


Combo box two when updated will then after update requery Combo box 3, and once field 3 is updated, the database query displays what is technically in another unbound form the result in Field 4.

This works wonderfully if I want to just temporarily display the information however I now want to retain this information and use it.

If I want to create a system where the values from each combo box update are saved, how would I best go about doing that?

Is there a tutorial or information you know if I could read up on?

Regards

[Micron]

Sounds like you're using what's known as cascading combos.

If I want to create a system where the values from each combo box update are saved, how would I best go about doing that?

Easiest is to use bound combos, which creates the situation where their values can be arbitrarily changed. Best might be to keep them unbound but you will have to use code to create the record(s). To do that, you need a trigger - likely a button click event which should first validate as many aspects of the values that you deem necessary. Likely the least would be which combos have values. You might want to disable/enable the button using the after update event of the last combo.

Are those your real field names?

[Steven19]

Hi Micron

They are indeed cascading combos

Not my real field names, I just wanted to explain it in simple terms to be understood.

Button enabling and disabling are easy enough on the last combo box. And keeping the combo's unbound is a good idea, and the functionality works well at the moment.

All I need really is a sample or an example of a trigger to work with and I can take it from there and adapt it accordingly.

[Micron]

So the trigger would be the button click event I mentioned?

[Steven19]

When I select from the Combo Box, I suppose the trigger could be the after-update event.

[Micron]

Then I guess you'd use that event to build a sql statement and execute it. You could do that all at once within that event, or as you go, using a form level variable. I presume it would be like an append query (INSERT INTO...VALUES...) but if a user can edit existing fields you'll need to code to use append or update.

All I need really is a sample or an example of a trigger to work with and I can take it from there and adapt it accordingly.

That means you're good to go now?

[davegri]

You might get some useful ideas from this:

Ultimate Dynamic Multiple Cascading Comboboxes, synchronized in any order (accessforums.net)