>>You could run GenDBC (should be under you VFP directory Tools\GenDBC) against your database to get the code implmentation of your view. With the SQL code, you could pull everything the results into a cursor and you wouldn't need a view.
>
>I need the view to Update the original tables.
>
Sorry I led you astray on this. Because you wanted this dynamic, I was going to tell you to clean up the view after use (i.e. delete view v_something). After reading the documentation on this, it says you can not delete a view without opening the database exclusive which is *really* bad in a multi-user environment so I switched in midstream to the cursor idea.

However, after some experimenting, you can delete the view without opening the database exclusively. In fact one user can have it open, and another user can delete it from the database. It will remain in the first user's cached memory for the Refresh timeout. Since this is incredibly bad, I wouldn't recommend the cleanup.

As an aside, if you create the view dynamically, set safety off just before creating it or you will get the nasty 'view already exists, overwrite?' message.