× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Did you try switching to server mode, as I suggested in my original message in this thread?

If server mode is out of the question, have you considered passing the connection handle as a parameter to the second program so it can re-use the same connection?


James Lampert wrote:
James Lampert wrote:
At present, the older program has no SQL CLI teardown at all, because
hadn't expected it to get in a fight with any other program, and because I wanted it to have the best possible response time with repeated calls.

How much tear-down do I need to do in the older program, to make it stop
fighting with the newer one? Is an "SQLDisconn" enough? Or do I need to do other teardown, like an "SQLFreeStm," an "SQLFreeCon," or even an "SQLFreeEnv"?

So far, the only option I've found that works is the "nuclear option," i.e., complete teardown.

That seems to cause a 5-fold increase in execution time for a fairly simple query. I don't think that's going to work out too well.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.