CheckConnection

[Ken Leach]

I am running CheckConnection with a true param, before every procedure in my app that uses the TOracleSession. I seems to be making multiple connections to the database even though the old connection is still valid?
Should I simply check the connected property and then call CheckConnection if that is false? Seems redundant? Suggestions? (I am running D5 and Oracle 8.1.7)

 

[Marco Kalter]

The CheckConnection procedure does not lead to new database sessions. Only if the 'old' session was killed a new session will be created. If the Connected property is False, you should not call CheckConnection. The purpose of this function is to check if a connected session is still alive.

------------------
Marco Kalter
Allround Automations

 

[Ken Leach]

I understand that is what it is SUPPOSE to do. However I would see multiple EXTRA connections when I placed a check before each call to a ToracleQuery to be sure the database connection was still there! I was there and working, but the check still opened a new one? I know that is not what it is suppose to do... I was wondering why?