>>Robert,
>>
>>Views are really to be used when your back end data is in SQL Server or Oracle. If you haven't worked with those two, you won't realize what a pain the the butt the data conversion is between VFP and native SQL data (especially in dealing with DATE and LOGICAL data types).
>>
>>Select statements have to be formatted completely different from native VFP Selects. Views do the dirty work for you in the background. They automatically convert SQL data types to native VFP data types and visa versa in the background. I don't think most programmers realize what lengths the VFP team went to for the view capability to work.
>>
>>This means you can use native VFP commands on SQL Server data once your view is created. Using a view on a native table has almost no benefits, except the example I gave you before in generating an updatable select statement.
>----
>Hi Ed and thanks for your reply. About two yeas ago, I used a view in a Helpdesk app I coded for the feds. I was using navtive vfp. Using the view was a PAIN in the butt. I learned a lot about views (information we all need to know), and now becuase of you and members of UT, I know I did not need to use views with the native vfp. What I have not done is use buffering with network
>apps. I know how to cursorsetprop(), but I am not sure where to put it.
>Should I let the Data Enivorment open my tables and code a cursorsetprop()
>in the clicked event of an EDIT key? I am not sure where I need to code:
>USE MYTABLE
>CURSORSETPROP() (my buffering)
>thanks again...all :)


Views are not that tough. Once done and you have code to generate them it's a snap for a hosed DBC.

I use a BizObject to define my data environment as well as the rules {functionality} that pertain to that data. That way it's always present when I drop it on a form for use.

The bizobject has a DataEnvironment Class that is set by me. All data is opened nodata thus it's fast to see. All forms will have in their activate a load for a parameter needed for a specific view.

This all works fast, and cleanly.

Views are your friend! Especially with the rush to big back ends. Switching between the two is a nightmare.

I have done SQL Server back end in FPW2.6. Now that was fun. This is kids stuff today.

__Stephen