Depending on usage, I create an _screen object that gets instantiated at startup and use it throughout for most operations. At the very least, I create the connection string in an _screen var and then can create it from anywhere.
JH -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vince Teachout Sent: Wednesday, March 05, 2008 10:19 AM To: ProFox Email List Subject: Cost of open connection handles? I have an app that I'm modifying. At start up, the app gets a connection handle to the main database and stores it in a public var, let's call it gonHandle, which is then used throughout the app. No problems there. I need to tie in a second database, which I've done. This database will be used for the occasional report. Most days, it won't be used at all. My question is this: Do I open and save a public handle at startup, or just get a handle when the actual report is needed. Others who maintain the program would probably expect the same behavior as the current reports (ie, a global handle is setup and ready when/if needed) Is there a high cost in performance, etc, with creating the handle and leaving it available through the program, or should I call as needed? [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]@shelbynet.com ** 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.
