>Hi,
>
>I implemented the approach of recovering a SQL Server connection using the access method of the connection handle.
>Example:
>connection handle is
>

>oApp.conn_handle
>

>Method:
>

>oApp.conn_handle_access
>

>
>I updated 7 customers with this change. I also enabled a quiet log of every time the connection is "recovered."
>So far, I noticed (after one day), that one customer had 3 entries in this log. No error messages. This is good.
>
>Now I would like to know which routines, or which CA objects, trigger the connection restore. Because I use this call
>=oApp.conn_handle from 3 methods of the CA class and I also use this call from the procedure that uses SQLEXEC() with a SQL Select statement. That is, I call the =oApp.conn_handle before the SQLEXEC()
>
>The only way I see to be able to track these calls is by creating an application property and setting a certain value. Then checking the value inside the oApp.conn_handle_access.
>
>Anyone can suggest an alternative method?
>
>TIA

Try PROGRAM() or ASTACKINFO()

Aunt Edit says:

Normally any code should run independent of the caller, or the caller must put be a parameter. For debugging it might be ok - but consider to use SET COVERAGE and something like CVP http://gorila.netlab.cz/cvp.html