Recordset object

Question

5.00/5 (1 vote)

See more:

Why do we set a recordset object to nothing after retrieving? What is the technical idea behind that?

eg.

VB

dim  rsTemp

set rsTemp = Server.CreateObject("ADODB.recordset")
' after that I retrieve some data
rsTemp.Open "select * from Rates" blah, blah

then I see something like this:

VB

set rsTemp = nothing

Why should we set it to nothing?

Posted 9-Dec-10 2:43am

Bassofa

Updated 9-Dec-10 2:47am

Sandeep Mewara

v2

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Henry Minute · Answer 1 · 2010-12-09T03:02:00

The usual reason for this is that the RecordSet takes up resources on the computer - memory, possibly clock cycles etc. so it is a good idea to dispose of it as soon as it has served its purpose so that it can be garbage collected and its resources freed up.

This applies to any object that your code creates. If the object implements IDisposable, you should also call its Dispose method.

Without seeing the context that your code example comes from it is not possible to tell if the assignment to nothing is necessary, but it is always a good idea to do it as soon as possible, rather than waiting for the framework to do it for you.

E.F. Nijboer · Answer 2 · 2010-12-09T03:06:00

The reason for that is because those objects weren't always destroyed like they should in past times. COM objects are normally automatically released when they get out of scope and have no references set to them. For some COM objects this was somewhat problematic in the past. For some it was necessary and for others (or other environments) it wasn't. But to simply make sure that it does, those lines where added to set them to nothing specifically. The recordset would need to be closed as well by the way. Also, if the connection to the database is still open and that object still has a reference to the opened recordset, then it is of course very likely that it isn't released until the connection is closed.

As what I know it shouldn't really matter for ASP because after the request is handled, everything (except maybe session data) is released.

Good luck!

Recordset object

2 solutions

Solution 1

Solution 2

Add your solution here

Preview 0