When I am using free tables to maintain compatibility with 'legacy' applications, I create a DBC with a single new table with a single field, and create the views in that DBC. Remember, the tables you use to create the VIEW can be free tables.

A more frequent technique I'm using these days is to base my selection grid on a CURSOR "tempcursor". In the Form's INIT I place code like:
Parameters SearchForMe
And then do an SQL SELECT to create the cursor with the desired subset of records in the Form's Init. Voila - you're not slowed down by a FILTER, your data set is small, and you can use the grid to select a record from the list. Of course, if you need to modify records within THAT form, you need to use VIEWS.

FWIW

>But I'm only using free tables. VIEWS don't apply to that RIGHT?