Can you provide a outline on how to use a view in a search with the new BrowseDialog or a sample?

Thanks for the sample; got it working and it's a lot easier than what I was doing before However there are a couple of quirks that would be nice if they could be fixed. First if you go back and edit a field that doesn't exist in the original table structure, the Search Field Criteria dialog doesn't "remember" the field name, it just defaults to the first field in the Search Field drop down. It also doesn't "remember" the Search Style which also defaults to the first field in the Search Field drop down. Second I was wondering if the DataType override is suppose to set the appropriate available Search Styles, currently it has no impact. To get the appropriate Search Styles when adding a view field, you first have to select a field of the same data type that exists in the original table as the view data type you're adding.

Yeah, I noticed this as well and it is already on the list.







No, this is for return types and casting. Most times this is never needed. We actually ended addressing some of the underlying issues that this caused within the class itself. But this just enforces the data type on the return values for testing purposes.