Results 1 to 2 of 2

Thread: Issues after upgrading SQL drivers?

  1. #1

    Thread Starter
    Hyperactive Member
    Join Date
    Dec 2005
    Posts
    323

    Issues after upgrading SQL drivers?

    Hi everyone,

    I am in the process of investiigating the impact of changing the MSDASQL driver connections to SQLNCLI10 drivers in the global.asp section of our site.

    It seems like when I do a stored procedure trying to read the .eof value causes the process to fail. Any ideas?

    Thanks,
    J

  2. #2

    Thread Starter
    Hyperactive Member
    Join Date
    Dec 2005
    Posts
    323

    Re: Issues after upgrading SQL drivers?

    Here's some more specifics:

    The code being executed is this:

    Dim SQLCmdValidate
    Set SQLCmdValidate = Server.CreateObject("ADODB.Command")
    SQLCmdValidate.ActiveConnection = SQLConn
    SQLCmdValidate.CommandType = adCmdStoredProc
    SQLCmdValidate.CommandText = "amp_AdTraffic_ValidateSpot "
    SQLCmdValidate.Parameters.Append(SQLCmdValidate.CreateParameter("CampaignID", adInteger, adParamInput, , Session("CampaignID")))
    Set RSValidate = Server.CreateObject("ADODB.RecordSet")
    Set RSValidate = SQLCmdValidate.Execute
    .
    .
    .
    .

    if RSValidate.EOF = false then
    .
    .
    .


    In my global.asa, if I am using the MSDASQL driver connection string, this works every time. The SP returns values that I can then validate against. Even if no records are returned, the RSValidate.EOF reads correctly.

    If i change the connection string to the SQLNCLI10 driver connection string, the SP returns nothing.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width