Activating OnSelect trigger from a list box

[#1]

Hi.

I am making an application for a customer in QV, and I have a small problem.

I have a list box with the option 'Always One Value Selected' activated.

I also have a field trigger with some actions, that I want to be made, whenever I select a value from the list.

My problem is, that the field trigger is not activated, when I select the same value again in the list box. Only if I select another value. Is there a way around this?

I thought of a fake value in the data, that could serve as a default value, but not shown in the list box, but I think that is a crappy solution. Any ideas?

Have a nice day.

Kind regards

H.P. Hansen

Denmark

[#2]

Have you tried applying the triggers to "On Select" option as well as the "On Change" option?

[#3]

Could you elaborate on what field triggers are you working on

[tresesco]

Possibly your trigger is set on 'On Change'. Change it to 'On Select'.

[#5]

I have tried to set it on both OnChange and on OnSelect. That doesn't make any difference. I am not sure that QV sees it as a selection or change, if you pick the same value from the list box (or the straight table, or whereever you click the value).

[tresesco]

Could you post a sample that demonstrates the issue?

[#7]

I have attached an example with 2 fields: Branch and Name. The field Branch have activated the flag 'Always One Selected Value'.

I have made a trigger OnSelect on the field Branch, and the purpose of the trigger is to switch to sheet 2.

Try to select a branch on the list. If you select the one already selected, nothing happens. If you select another, you swap to sheet 2.

[tresesco]

This behavior can be explained like this: when a value is selected in a listbox, if you click on it again, qv interprets it as 'user wants it to get deselected'. Once you have 'Always One Selected Value' enabled, qv tries to deselect in vain. So, qv is not getting any action 'On Select' or 'On Change' to be true. Hence the trigger is not fired.

[#9]

That is exactly the problem.

Can you think of any way around this, without having to code some crappy things, with fake values and such...?