See - perserverance pays!

>Terry,
>
>>I guess the COM wanted the connection open:-).
> :)
>
>>There used to be a guy on this board, JVP, but he is no longer >participating. However, he has written some [very good] white papers:
>>
>>http://msdn.microsoft.com/library/default.asp?url=/library/en->us/dnfoxgen/html/adojump.asp
>
>Thanks, I read it and bookmarked it. It gives the same info that I've been seeing all week, except it's all on ONE PAGE!!!!
>>
>>Who is "rush/html/Admin_UserEdit.asp"? Is this your COM, or a vendor's?
>
>That's an ASP page used to edit a record.
>HOWEVER...
>
>I have eliminated the problem, and it looks like this:
>
>Dreamweaver 'automatically' creates the ADO code necessary to create and reference a Recordset, based on some parameters you give it. It DOES NOT, however, create a discrete ADODB.Connection object via
>
>Set oConn = Server.CreateObject("ADODB.Connection")
>
>This means, apparently, that you can Close() the Recordset but NOT, the Connection.
>
>Solution:
>I added a Connection opener immediately BEFORE the Recordset is created:
>
>Dim oConn
>Set oConn = Server.CreateObject("ADODB.Connection")
>oConn.ConnectionString=MM_RushForms2k3_STRING (include File: VFPOLEDB provider)
>oConn.Open
>
>Then, at the end of the page where the Recordset is Closed(), I also Close the Connection:
>
>oConn.Close()
>Set oConn = Nothing
>
>Thanks again for the ear and the direction. It helped me solve this problem.
>
>David