Advantage Database Server

I have to pass some data from Advantage Database Server (a database wich is
used generally with Delphy) to SQL-Server.
In order to create a Linked Server from SQL-Server to the above mentioned da
tabase- what should I do?
If there is an ODBC for the database- should it be installed on the server o
f the SQL-Server or on my terminal?Yeah...if I remember right from using it before, you need to
install the drivers and ole db provider on SQL Server. Then
you can create the linked server to the Advantage server.
They should have information in the help files on this or
else on the web site.
-Sue
On Wed, 23 Feb 2005 19:41:08 +0200, "Geri Reshef"
<gershon_reshef@.recanati-alum.tau.ac.il> wrote:

>I have to pass some data from Advantage Database Server (a database wich is
used generally with Delphy) to SQL-Server.
>In order to create a Linked Server from SQL-Server to the above mentioned d
atabase- what should I do?
>If there is an ODBC for the database- should it be installed on the server of the S
QL-Server or on my terminal?

Advantage Database Server

I have to pass some data from Advantage Database Server (a database wich is used generally with Delphy) to SQL-Server.
In order to create a Linked Server from SQL-Server to the above mentioned database- what should I do?
If there is an ODBC for the database- should it be installed on the server of the SQL-Server or on my terminal?
Yeah...if I remember right from using it before, you need to
install the drivers and ole db provider on SQL Server. Then
you can create the linked server to the Advantage server.
They should have information in the help files on this or
else on the web site.
-Sue
On Wed, 23 Feb 2005 19:41:08 +0200, "Geri Reshef"
<gershon_reshef@.recanati-alum.tau.ac.il> wrote:

>I have to pass some data from Advantage Database Server (a database wich is used generally with Delphy) to SQL-Server.
>In order to create a Linked Server from SQL-Server to the above mentioned database- what should I do?
>If there is an ODBC for the database- should it be installed on the server of the SQL-Server or on my terminal?

ADODB and Mirrored SQL-Server

I did setup a Mirrored Database. Connecting from it using ADO.NET works well. It goes to the Mirror if the Principal fails.

But ADODB does not work. I get the error following error:

80004005 Invalid connection string attribute

When trying to connect to the DB in case the principal failed and the mirror is active. (MyProductiveDB is in failover state)

What do I do wrong?

Here is the code:

ADOConn = New ADODB.Connection

ADOConn.Open(CS)

CS is my Connections-String:

"Provider=SQLNCLI.1;Data Source=MyProductiveDB;Failover Partner=MyMirror;Initial Catalog=MyCat;Persist Security Info=True;User ID=MyUser;Password=xxxxxx;Pooling=True;Connect Timeout=5;Application Name=MyApplic"

Remark: When I try to add "Network Library=dbmssocn" to the connection String, I get the same error, even if the Principal is active.

Your help is very much appreciated.

Beat

I contacted the client team and they pointed out that Pooling is not supported in SQLNCLI.

Regards,

Matt Hollingsworth

Sr. Program Manager

Microsoft SQL Server

|||

Beat,

Do you mind if I ask for a sample of your ADO.NET code that works well if the principal fails?

Thank you very much.

|||?

ADODB and Mirrored SQL-Server

I did setup a Mirrored Database. Connecting from it using ADO.NET works well. It goes to the Mirror if the Principal fails.

But ADODB does not work. I get the error following error:

80004005 Invalid connection string attribute

When trying to connect to the DB in case the principal failed and the mirror is active. (MyProductiveDB is in failover state)

What do I do wrong?

Here is the code:

ADOConn = New ADODB.Connection

ADOConn.Open(CS)

CS is my Connections-String:

"Provider=SQLNCLI.1;Data Source=MyProductiveDB;Failover Partner=MyMirror;Initial Catalog=MyCat;Persist Security Info=True;User ID=MyUser;Password=xxxxxx;Pooling=True;Connect Timeout=5;Application Name=MyApplic"

Remark: When I try to add "Network Library=dbmssocn" to the connection String, I get the same error, even if the Principal is active.

Your help is very much appreciated.

Beat

I contacted the client team and they pointed out that Pooling is not supported in SQLNCLI.

Regards,

Matt Hollingsworth

Sr. Program Manager

Microsoft SQL Server

|||

Beat,

Do you mind if I ask for a sample of your ADO.NET code that works well if the principal fails?

Thank you very much.

|||?

ADO/SQL error -2147217900 (80040e14)

With the below procedure I want to run a stored procedure on a SQL-server 2000, but for some reason I get run-time error -2147217900 (80040e14), stating that the stored procedure doesn't exist.

As it does exist, the connection is open, and running the code in query analyzer works, I center the problem down to the database being used.

But whats wrong? The user and database has been added to the system dsn AccessSQL, user and passwords works fine in query analyzer.. yet for some reason it apparently sends the ado command to the wrong database, and thus can't find the stored procedure.

Thanks in advance,

Trin

Dim forbindelse As New ADODB.Connection
Dim kommando As New ADODB.Command
Dim pam1, pam2 As ADODB.Parameter
Dim forbindelseDSN As String
Dim strSQLland As String
Dim strSQLtid As String

forbindelse.Open "DSN=AccessSQL;APP=Track Exporter;Database=Gramex_UDV;Network=DBMSSOCN;", "aaaa", "tttt"
kommando.CommandText = "TRACK_EXPORT_sp_opdatland"
kommando.CommandType = adCmdStoredProc
kommando.ActiveConnection = forbindelse
Set pam1 = kommando.CreateParameter("land", adChar, adParamInput, 2)
Set pam2 = kommando.CreateParameter("org", adChar, adParamInput, 4)
kommando.Parameters.Append pam1
kommando.Parameters.Append pam2

pam1.Value = "'" & kombo_land & "'"
pam2.Value = "'" & kombo_org & "'"

kommando.Execute

forbindelse.Close
Set kommando = Nothing
Set forbindelse = NothingFYI I've attempted with a different connectstring:

forbindelse.Open "provider=SQLOLEDB;Data source=GRAMEXFIN;initial catalog=Gramex_UDV;User ID=AccessBruger;Password=gramex"

Same error...

I've rechecked that the login has execute permission for the stored procedure...|||Problem solved - Turns out the database was setup to use full qualifiers for the object name.

In this case the stored procedure was to be adressed with its dbo... ket.TRACK_EXPORT... etc. etc..

/Trin