Keith..

You snipped the quote out of context. The statement below was couched in the context of the tight binding that exists between the server and the client that is manifested as a RV. With that in mind, my response, which BTW, was a month ago, was/is 100% relevant...




>> ... That's why if you change a field name on the server, you can no longer modify the view. If you were using SQL Pass Through instead, you would not have this problem.
>>
>
>John,
>
>I can't see how this has any relevance to Patrick's problem. You are attempting to hijack Patrick's legitimate question into another RV-SPT debate. Please take it elsewhere...
>
>
>
>Patrick,
>
>One way or another, the user's identity has to be validated by the server before they can access the data.
>
>If you are using RV's and you are on a 100% windows network, you can set the connection to use the NT domain account automatically. Then you can leave the USER and PWD fields blank in the connection string.
>
>Another method is to store the connection string in a local VFP table. Using built-in windows cryptography, you can encrypt the user name and password in this table. Then you can create a separate developer-only application that knows the encryption key and has an interface for modifying the connection string.
>
>Good luck!
>
>- Keith Payne