>>>>>You cannot keep the remote view on the SQL server, because it is a part of VFP database which may be on local PC or somewhere on the network.
>>>>------------
>>>>ok - so the best and the fastest way to do this, is to have the remote views
>>>>on the user's pc, delete the contents of the remote views when the user
>>>>exits the program, and update the views when the program is loaded.
>>>>it that right?
>>>
>>>You can do this, but I don't understand why would you delete the data on the server every time the view is populated?
>>--
>>I am not going to delete the data on the server, I would just delete the
>>data in the remote views for security sack. These remote views live on the
>>user's pc. what do you think?
>
>I see. But the remote view is just a SELECT... FROM... INTO CURSOR definition, it does not contain the data by itself. When you open the view, it populates the cursor which is just a temporary table, and when you close it is gone. Of course, if the view cursor is big, part of it may be swapped to the hard drive. If you care that there may be some data left by any chance, make sure you delete all files in the directory which is specified as temporary dir for VFP.
---
I see - a remote view is a remote view and you can not use it like a local
view. (I thougt you could). I re-invoked vfp60 and open my database and tried
to brow on my remote view and without a network connection, it would not work.
I see not, ok - thanks :)