Views can't use a connection created with SQLCONNECT(). You have to create a connection in the database that contains the view. You can use CREATE CONNECTION to create the connection and DBSETPROP() to set its properties. When you create the view, use the connection you created.

>Ok, so it goes like this: 1)build my own form to get the name/password, 2) stuff name/password into an SQLCONNECT(). If DispLogin is set to 1 or 3, then subsequent connections will not bring up the ORACLE dialogue. Right ?
>
>What I can't figure out is: if I establish a connection using SQLCONNECT(cConnect), why is it not recognized when I follow it with CREATE VIEW CONNECTION cConnect. Do I end up with 2 connections to the backend ?
>
>
>>You can put your user name and password into your connection. Then set the >connection's DispLogin property to either 1 or 3. That will prevent the login >dialog from displaying when the information has already been entered.
>
> >I have set up a little routine which rebuilds all my remote views programmatically. It works fine, except I have to log on (ORACLE) for each and ever view. This is a pain in the butt. About the only good thing about it is that I will never forget my password.