Connection Variables

Results 1 to 2 of 2

Thread: Connection Variables

  1. #1
    Sharon B. Guest

    Default Connection Variables

    I’m just wondering why is it that with some (co-shared) NT servers I get the following error once I define the word/variable “Conn” to trigger my ADO database connection.<BR><BR>For instance in some NT servers when I type:<BR>&#060;%<BR>Set Conn = Server.CreateObject("ADODB.Connection")<BR>Conn.Op en "Provider=Microsoft.Jet.OLEDB.4.0; Data Source=D:InetpubNTaccountDatadatabase.mdb”<BR>%& #062;<BR>I get the error:<BR>Object doesn’t support this property or method “Conn”<BR><BR>However when I define another variable such as:<BR>&#060;%<BR>Set Whatever = Server.CreateObject("ADODB.Connection")<BR>%&#062; <BR>I don’t get the error.<BR>Is this because someone else (on my co-shared Web-hosting server) is using this famous typical connection variable name (“Conn”) and therefore it’s already preoccupied? …Or what?<BR>And if so why?<BR> <BR>

  2. #2
    Join Date
    Dec 1969

    Default RE: Connection Variables

    I ran into this same problem. However, it only seems to return an error when trying to use a MS Access database. The word "Conn" must be some type of reserve word in Access. I changed my connection variable to "oConn" and everything works fine. Sorry I can&#039t give you a more detailed explanation for the error.

Posting Permissions

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