>>That is easy on our machines but what about distributed systems? What about security in the database? Will you allow that out to the desktop realm? This gets into a very scary issue.
>>
>>Also how do you update that id/password comination in the future as corporate mandated password changes are followed?
>>
>>__Stephen
>>
>>
>
>I have a VFP login form to temporarily capture the user's ID and Password. I then create the connection string needed to open a shared connection. I have a User's table in the DBC where I lock the file while I do a DBSETPROP on the Connection's ConnectString. I open a dummy remote view just to establish the connection. I then execute DBSETPROP again to remove the Connectstring, then unlock the table. Since this takes just a few seconds, user's trying to connect at the same time are not inconvenienced too long.
>
>The dummy remote view is open the entire session of the application so I never have to have the user's ID and password. I release these 2 values after opening the dummy view. All safe and secure, no embedded IDs and passwords in the connection or in tables.

Thanks. That's a nice clean approach to this. My last employer was fanatic about changing passwords and this was a BIG issue. We were only in FPW2.6 with SQL Server data at the time so dbsetprop() was not an option.

__Stephen