Jim,

Well, it depends on how you are using it. If you only have the connection in the database for your remote views, then no, you won't need to do a SQLCONNECT. But, if you use it for both the remote views and SPT, then yes, you'd still need to SQLCONNECT() for SPT, but not for the remote views. CREATE CONNECTION simply creates a saved connection in the database. Your remote views will use that saved connection.

HTH,
Chad

>Chad,
>
> I like the 2nd suggestion better. After I create the connection, do I have to connect it by using SQLCONNECT(...) or is that automatic?
>
>Jim
>
>>Hmmm,
>>
>>Well then, I'd suggest you create a single userid/password in SQL that your app connects as and hard-code that into the connection or use trusted connections (I think you can do that in a saved connection) and go to SQL as whoever is logged into the PC.
>>
>>OR (just thought of this) and this may be your solution:
>>
>>Why not just recreate the connection each time you need it:
>>
>>DROP CONNECTION ProdSQL
>>CREATE CONNECTION ProdSQL USERID usr PASSWORD pass ...
>>
>>You can do a CREATE CONNECTION and feed it the parameters or a connection string.
>>
>>HTH,
>>Chad
>>
>>>Hi Chad,
>>>
>>> I've created remote views in my application and those connect via a connection. That's why I need one...
>>>
>>>Jim