Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Arrays 1

Status
Not open for further replies.

leonepaolo

Programmer
May 28, 2001
82
0
0
CA
Hi!

I know it's important to close recordsets and connections and set them to nothing when we're done with them.

Is there a need to erase arrays as well?

Thanks in advance,
Paolo
 
Once you leave their scope they are abandoned anyway.

So if you create an array within a sub routine, once you exit the subroutine they are free for anything else to inhabit. If they are global variables, then they are free once you exit the application.

So on...

So i would say. Only if you are defining massive arrays with a global scope then it would be a good idea to erase them.

-Pete
 
yes Pete, but connections and recordsets, should be
closed & set to nothing. I believe Access attempts to
"Nothing" them, at the end of a procedure, but
may fail.(something like that)
LEAVING THEM OPEN, CAN SLOW DOWN YOUR APP.
 
Right Zion...but he already said he knew that...so i didnt address it.

-Pete
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top