The view designer has always be a little flaky. FYI, I was able to replicate some flaky behavior like you mention. You can create the view with code if you want or instead of using LIKE just use = (but remove the percent sign from Unrepaired%).

CREATE SQL VIEW "TEST" ;
AS SELECT ProductID, ProductName FROM Products WHERE ProductName like 'C%'

After creating the simple view, you could then modify view to set the other properties (or use DBSETPROP(), see gendbc output for an example).

>While using the View Designer, I select the new "Like" option on the filter tab and set the text to 'Unrepaired%' ... I was expecting that this action would show all of the records that started with the word 'Unrepaired' however, the data set comes up blank. I then selected 'View SQL' and saw that the SQL statement had used the '=' sign instead of the word 'LIKE' so I replaced the equal sign with the word 'LIKE' in the SQL statement and re-ran the query from the SQL page using the run (!) button. When I did this, I git the result data set that I expect. However, whenever I exit the SQL statement the "LIKE" is always replaced with the '=' sign and then I get the an empty result set when run from the main View Designer screen using the same run(!) button. FYI ... "Like" still shows up on the View Designer grid eventhough the text in the SQL statement keeps switching back to and equal sign.
>
>I know that in native FoxPro that a single '=' sign works similar the SQL 'LIKE' keyword and that the double '==' will locate only an exact match. So, I wasn't that surpised when I saw the 'LIKE' selection translated to the single equal sign but its just not giving me the correct answer. But, forcing the work 'LIKE' into the SQL statement works like a champ!
>
>Any ideas?
>
>Thanks,Robert