>I know that much about views have been discussed here, but here it is again. I am requesting all opinions here.
>
>Because of the limitations of the view designer, I'd prefer to use commands to create all of my views when needed by a form, even the simple ones to maintain consistency. Where is the best place to issue the CREATE VIEW command. As a stored procedure? As a method to a class? Within the DE of a form? How best to get it into the DE of a form if created outside of the form? What are the pros and cons of any particular method used?
>
>What is the best way to create parameterized views assuming that the parameters will be somewhere available probably as a field on a form?
>
>The database needs to be exclusive when issuing CREATE VIEW. Is everyone putting a local copy of the *.DBC on the client? How best to maintain this if table defs change?
>
>I've read the Extending Methods and Indexing View article in the VFUG Newsletters as well as the Introduction to Client-Server Development in VFP.
>I've also been through the MS Knowledgebase and read
>pertinent articles on views. Non seem to indicate exactly how to design a well maintainable app using views.
>
>Any and all help with the implementation of views in an application will be greatly appreciated. Thanks,
>
>Steve Despres
>EZ Data Inc.
>sdespres@erols.com

I use the View designer for views which are simple and SQLEXEC for selects that are more complex. When I change the SQL Tables, I modify the views and distribute a new DBC to the client, who then distributes that to each user machine. There are less than 50 user machines at this time, so although it takes a little time, it is not bad.