5 replies to this topic

[gdmjdkc]

I have a combo box that I limit list choices from a table based on previously entered information. The desired choices appear in the combo box list and all looks well until the user enters a choice directly from the keyboard instead of using the mouse. It allows them to enter a choice even though the choice is not in the list. If it is a valid choice in the table it allows the input even though it has been filtered out of the list.

I have been able to force the user to use the mouse to select from the list and not be able to type directly into the combo box, but for obvious reasons this is not the most desirable solution.

I have code in the selection cycle of the combo box that limits the list of choices and I could maintain another identical set of code to check input if the user typed directly into the combo box, but that would mean maintaining 2 sets of code to do the same thing. Also not the most desireable solution.

Does anyone know an easy way to limit the user input to only valid choices in a list?

[Joseph Bove]

gdmjdkc,

One solution is to simply read the table after the field is processed to verify that the record is valid.

hth,

Joseph

[gdmjdkc]

Thanks for the response Joseph, but I am doing that. I didn't make myself clear so I will take another shot at explaining the situation.

The records are valid, they are in the table, but I have excluded them programmatically based on other information the user has entered before displaying the combo box list. If I force them to pick from the list everything is great.

The problem is that when I allow them to type directly into the combo box. If the choice is not displayed in the list it still accepts it as long as it finds a record in the table.

I want to be able to block them from typing in a choice that is not in the list without having to maintain two sets of code that handles the exclusion.

A possible solution would to be to create a temp file and only populate that table with valid choices, but that is not a desirable solution either. I am hoping for a better solution.

[Chris Mackenzie]

You might try this:

Use the same logic ID in the cycle populating the list and in the cycle
with the combobox, check value of @CURLSNAME and either DSEL if
building list or issue a message and return to the input field if selecting.

[andykay]

How about building an array with the valid selections in it, drive the combobox from that array, then in the LOGIC AFTER of the field compare the value in the field itself with those values in your array. If you find a match then great, if not...issue them an Error.

TWIWD,

AK
(That's What I Would Do)

[Joseph Bove]

gdmjdkc,

The end user experience would be slightly different, but you could use a listbox instead...

hth,

Joseph