I'm with Virgil on this one. I always close them even if I am randomly creating the names. I would hate to have to debug something where it was a duplicated random cursor and I have had problems with code where the names have been 'made up'.
My framework also has its own routine when a form closes to clean up any strays (thought I'd keep to that farming metaphore ;] ) Regards Michael Hawksworth -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of MB Software Solutions Sent: 14 May 2007 03:43 To: [EMAIL PROTECTED] Subject: Cleaning up temp cursors When you're done with temp cursors you've created, do you explicitly close them or do you just leave them (whereby they'll be implicitly closed later at some time during a CLOSE TABLES ALL, CLEAR ALL, or similar command)? I would think it'd be better to explicitly close them, but wondered about the consensus here. If a cursor took up a huge amount of space (i.e., large record size with high record count), then I could see closing it explicitly, but most of my temp cursors are really small in size and as such wouldn't be hogging up much resources. -- Michael J. Babcock, MCP MB Software Solutions, LLC http://mbsoftwaresolutions.com http://fabmate.com "Work smarter, not harder, with MBSS custom software solutions!" [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
