>Do you know where i could find detailed info on the DSN-less connection?
Unfortunately I haven't found a place and/or book with lots of information about this. The information seems to be scattered in several places. This is part because each provider (e.g. SQL Server, Oracle, Pervasive) uses its own parameters.

For SQL Server, you can probably find something in SQL Server books for administrators.

Try using a connection string like this and see if that helps you solve the problem of configuring the SQL Server client libraries:

DRIVER=SQL Server;SERVER=Ovsps_TCP;uid=;pwd=;APP=Fap;DATABASE=fap;Network=DBMSSOCN=Address=;

>This is my connection string
>DRIVER=SQL Server;SERVER=Ovsps_TCP;uid=;pwd=;APP=Fap;DATABASE=fap;
>
>Apperantly i have to read more about DSN-less connection.
>Do you know where i could find detailed info on the DSN-less connection?
>Thanks.
>Kamil.
>
>>I don't know how your DSN-less connection string looks like, but I think that what you are missing is the "address" and "network" parameters in the connection string.
>>
>>Address could be an IP address, followed by ",1433" which is the port that SQL Server listens to.
>>
>>Network indicates the network library that the SQL Server ODBC driver will use. It refers to the actuall DLL that the ODBC driver will use.
>>
>>For example a network value of "DBMSSOCN" will use "DBMSSOCN.DLL" to connect to SQL Server via TCP/IP. A value of "DBNMPNTW" will use "DBNMPNTW.DLL" to connect to SQL Server via Named Pipes.
>>
>>

>>cConnStrin = "SERVER=123.123.123.123;DRIVER=sql server;" +;
>>             "UID=sa; PWD=; DATABASE=northwind;" +;
>>             "Address=123.123.123.123,1433;" +;
>>             "Network=DBMSSOCN"
>>
>>nConnHandle = Sqlstringconnect( cConnString )
>>
>>