But if I do that - then I need two sets of views though right? One set of local views (for VFP tables) and one set of remote views (for SQL tables). Then on top of that I'd have to write some gizmo to deal with all the control sources of all the controls on my forms and reports because those would change as I'd be dealing with two sets of views. Using my approach it's the same view either way so all those problems don't exist. ....or am I misunderstanding something??


>You can do that now but with Local Views. Look at the OpenViews property of the data environment of the form. Just switch it between local and remote. It's easy and you can use all the power of VFP files.
>
>>It's a long story - but in a nutshell it's so I can switch backend databases. I change the connection string for SQL server or for VFP tables - so I'm able to use the same remote views. I know it sounds weird but it's worked for me pretty well. Obviously the tables have to be designed properly - but with a little planning it's pretty slick.
>>
>>
>>>Why do you have a remote view to a VFP table?
>>>
>>>>I have a remote view that connects to a VFP table (yes I know that seems odd).
>>>>
>>>>My problem is that the remote view is excluding the deleted records - which in an ideal world would be fine - however in my case I'd actually like to see them. I tried the old SET DELETED ON and SET DELETED OFF thing - but same results.
>>>>
>>>>So is there anyway for me to see the deleted records in the remote view?