use myDBC!mySQLServerView ;
 connstring "Driver=SQL server;Server=ServerName;"+;
  "Trusted_connection=Yes;Database=myDatabase"
* Or
use myDBC!mySQLServerView ;
 connstring "Driver=SQL server;Server=ServerName;"+;
  "Integrated Security=SSPI;Database=myDatabase"

Cetin

>I guess I'm not making myself very clear here. It's the pwd variable I'm uncertain about.
>
>The windows userid is available, but how about the password? I don't want them to have to log in to this particular app, but neither do I want them all to log in as JaneDoe & PassWord on the sql server.
>
>In short, the login should be the users windows login on a trusted connection.
>
>>Use myDBC!mySQLServerView ;
>>connstring "Driver=SQL server;Server=ServerName;"+;
>> "User ID=uid;Password=pwd;Database=myDatabase"
>>Cetin
>>
>>>Cetin,
>>>
>>>You are the other one :-)!
>>>
>>>I'm actually a bit ashamed about asking the question in the first place, instead of looking up the USE command.
>>>
>>>I have not tried it yet, but if it does not require exclusive access to the VFP DB, it's a workable solution.
>>>
>>>I've never had any reason to use connection strings, so I've always used defined connections line Connection1 in the DB.
>>>
>>>How does one handle userid and password in connectionstrings?
>>>
>>>>>Sergey,
>>>>>
>>>>>Might as well ask you directly, since you're the one that answers most of my questions anyway :-)
>>>>>
>>>>>Assume two SQL Server DB's, DB1 & DB2 that are 100% identical.
>>>>>
>>>>>Also assume one VFP DB, containing remote views only.
>>>>>
>>>>>Is it possible to let these views point to DB1 or DB2 respectively, or must I redo the whole thing and use SQLPT?
>>>>>
>>>>>TIA
>>>>>
>>>>>Regards
>>>>>
>>>>>Peter
>>>>Indirect answer :)
>>>>Use command has a CONNSTRING clause in VFP7 and up.
>>>>Cetin