I've got a number of dropdown search windows which use lastname+", "+firstname
displayvalues. After much pain, I finally noticed that the DropDownSearch service
was stripping the comma out of any displayvalue it found in the dddw source. When
this happens, you get validation errors on what appears to be a valid dddw entry!
DDSearch leaves commas alone as long as they don't match up with the DisplayValue, and
it returns the matching displayvalue -minus the comma- as long as you keep entering
matching characters. Unfortunately, that's not good enough for the column validation
and it triggers an error.
If you select the column from the dropdown list using a mouse or cursor keys,
everything works fine. The problem only occurs when you start using dropdown search.
Before I go mucking around in the dropdownsearch service, does anyone have any idea
why this is happening? Or better yet, does anyone have a workaround (besides using
fname lname or lname / fname!)
TIA,
Marvin Young
[EMAIL PROTECTED]
> [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE COMMANDS, ADDRESS
> A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE: help pfcsig
> SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]
