Dan, this is simple to do.

1) Create a new FilterWindow, inherited from pfc_FilterWindow window.

2) I cannot recall whether or not there are SLEs or DWs for the various fields, but in whichever event equates to the ItemChanged event, you call your validation routine and make any changes required.

After the new year I will try to remember to post better details.

Oln

I do understand, but if you take the just a little bit of time you'll find that the FilterWindow piece is pretty much self-contained.

Still, I get it....  :)

Olan

Dan,

Have you had a chance to look at PowerFilter?

http://powerbuilderui.com/powerfilter.html

From your description it sounds like you need a method to 'cleanse' a string to either eliminate or substitute 'bad' characters.  If this is the case you would need to accept the input then run it one character at a time through your method and return the character to be put back into the string.

One approach I have seen for this is to look at the ASCII values of the string (assuming you are not using Unicode) and eliminate (return an empty string or '') everything outside the range of values for lower and uppercase letters, numbers, and whatever other characters you deem acceptable.

So then the user cuts and pastes bad string into your app, app takes the string and 'cleans' it, 'clean' string is put into the control the user put his stuff, 'clean' string is put into the filter, filtering is done, etc.

If you end up coding your own filter window, there is a Windows API function that will clean the text.

https://docs.microsoft.com/en-us/windows/desktop/api/winuser/nf-winuser-chartooemw

Dan,

You may want to consider putting in a popup prior to the filter window opening that explains the different issues they may run into. Give clear examples of what's ok to use, and what will certainly fail. Give them an option in settings so they can turn the reminder off. Do NOT put a checkbox on the tip window to prevent it opening, they'll likely not read the window, and just tick it and keep going.

It would be helpful to submit a request for a new event "preValidate" so we could inspect the string and make any automagic adjustments prior to it's being parsed.

I've used the pfc filter simple window and don't like the way it populates the dddw's. It takes the sql and then repeats every select to populate them. In our case that was too slow, since the original select of the dw to be filtered already was a bit slow. It's much better to do something else like NOT populating the dddw's and just let the user type what he/she's looking for, untill the user decides he wants an existing value and therefore clicks on the arrows to show the dddw. In that case I scan the values of the already retrieved dw to populate the different values, rather than doing retrieves.

Just a tip if you decide to use the pfc filter window.