I'm borrowing some dreamweaver scripts in a large application. The end of one insert script reads:

  Set MM_insertCmd = Server.CreateObject("ADODB.Command")
  MM_insertCmd.ActiveConnection = "strConnect"
  MM_insertCmd.CommandText = MM_insertStr
  MM_insertCmd.Execute

As I understand it, this creates a new connection to the db.
If I afterward then do this:

Set MM_insertCmd = nothing

will that not only eliminate the command object from memory, will it also close the db connection? Is it necessary to somehow close the connection first, before setting the command object to nothing? Or will simply setting it to nothing "kill two birds with one stone"?

Thanks for any help.

Hi there,

Yes, this way of setting to nothing does release the command object from memory. The connection has to be explicitly closed using Close() method of the connection object.

Closing connection is done using,
ObjCONNECTION.Close()

Hope that helps.
Cheers!

_________________________
- Vijay G
Strive for Perfection

Thanks for the reply . . .
I'm not still not sure, though, how to close the db connection since I don't have an ObjCONNECTION object. How could I use the close method for an object I don't have? The only thing I have is a command object for which the last method was .execute

Is ObjCONNECTION.Close()a function that I can use, as is, without
defining ObjCONNECTION an object or variable? Is that all that is necessary?

Sorry, I'm just a beginner.
Thanks

Hey,

Well, if you get no error when you execute the command without opening the connection first, you won't get one when you close it. Ideally, you would do:

objCommand.Connection.Open()
objCommand.ExecuteNonQuery()
objCommand.Connection.Close()
objCommand = Nothing

Brian

I am not sure if Brian's suggested code would work. I assume that code pertains to ADO.Net and cannot be used for classic ASP. If wolfpack391 is looking for Classic ASP code then ADO command object supports only the following Methods.

Cancel - Cancels an execution of a method
CreateParameter - Creates a new Parameter object
Execute - Executes the query, SQL statement or procedure in the CommandText property

Though it works without having a connection object, for closing the connection explicity later, I would suggest you to use a connection object initially and then a command object, and finally close connection object, if you are looking to do that.

You can take a look at ADO Command Object. Also I would suggest you to take a look at the ADO Objects Hierarchy/Model for better understanding. ADO Object Model

Hope that helps.
Cheers!

_________________________
- Vijay G
Strive for Perfection