Home-grown ActiveX & SQL Server 7.0

Results 1 to 2 of 2

Thread: Home-grown ActiveX & SQL Server 7.0

  1. #1
    Join Date
    Dec 1969

    Default Home-grown ActiveX & SQL Server 7.0

    We are using home-grown ActiveX objects as a middle tier in out n-tier web applications. The object is instantiated by the ASP and then a call is made to a method that creates an ADO connection to a SQL Server 7.0 database (ADO v2.5). The connection process itself takes about 12-15 seconds, which is way too long. If I connect to the same database in the ASP (using VBScript), the connection takes considerably less time (less than 1 second).<BR><BR>Any ideas what might be causing this?<BR><BR>Thanks<BR>Tim Smith<BR>Senior Application Developer<BR>Golf Digest Companies<BR>Trumbull, CT <BR><BR>

  2. #2
    Join Date
    Dec 1969

    Default RE: Home-grown ActiveX & SQL Server 7.0

    Could be a bug in the code, your connection string.. If you are positively sure that its the ado connection object that is causing the delay.. ( through debugging ) then I recommend updating mdac and try messing around with a different provider just to see if its your connection string... Im not sure why if using the same version of ado it would make a difference whether it was called from asp or vb... unless something was different...<BR><BR>Heres a link that may help...<BR><BR>http://www.able-consulting.com/ADO_Conn.htm

Posting Permissions

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