Re: Ado and Stored procedure params destroy problem

From: "Vladimir M. Zakharychev" <bob--nospam--@xxxxxxxxxxxxxx>
Date: Wed, 31 May 2006 14:30:19 +0400

"Alen Cappelletti" <cocker@xxxxxxxxx> wrote in message
news:1149067685.442279.157640@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

To free the resources no longer utilized and give
the garbage collector some food to feast upon?

?? It's an error? Only destroy recordset?

Generally speaking, it's an error not destroying
any objects you created once you are done with
them. However, as the variables go out of scope,
epilogue code can destroy them automatically, or
GC can clean them up some time later. It all
depends on runtime implementation and I am
not very well versed in how VB does it.

--
Vladimir M. Zakharychev
N-Networks, makers of Dynamic PSP(tm)
http://www.dynamicpsp.com

.

References:
- Ado and Stored procedure params destroy problem
  - From: Alen Cappelletti
- Re: Ado and Stored procedure params destroy problem
  - From: Vladimir M. Zakharychev
- Re: Ado and Stored procedure params destroy problem
  - From: Alen Cappelletti

Prev by Date: Oracle form builder automatic increment while inserting new row
Next by Date: order by problem with stored procedure
Previous by thread: Re: Ado and Stored procedure params destroy problem
Next by thread: JDBC Driver setObject() converts empty string to NULL
Index(es):
- Date
- Thread