I'm running into a problem with manually trapping issues with situations where the value stored in a field is not in the list of values in a dropdown list.  With a normal ASP dropdownlist control I can use TRY CATCH and handle it just fine, but with the strata frame dropdownlist control it doesn't seem to trap the error and I end up with an unhandled error.  Since our users can edit the dropdowns in the system, they can remove codes used in the past (even though we heavily recommend against it, they demand the ability), VFP just gives them a blank in that situation.  I need some way to do the same type of thing in the browser, or at least not have the application crash when it hits one.

What can I do to avoid this (can't use the native data binding since we bind to different tables at runtime depending on what the user chooses to view/edit)?  It's so nice to just setup a method in a business object to populate the dropdown and such, but if I can't solve this I don't know if I can use the strataframe dropdowns, much as I want to.

This is with version 1.6.1 btw, being actually in testing for release (which is how we found this) is not a time to move to 1.6.5 even if it's a likely fix for the problem.