**

I have created a SQL call inside an active link that is connecting to a remote database and bringing back information that is viewed in Remedy. I would like to end the active link if the conection to the remote databse is unavailable. How could I also either end the SQL call being processed in the Activelink and also display a message saying remote database unavailable?


20060125This posting was submitted with HTML in it

**
I don't know of anyway to "cancel" an AL once it has started, but when I have the situation you describe, I have a "test" AL that runs first.
So at 100 I have an AL that runs a count or some other real quick query to the same table and have it set a field - I use that field as the part of the qual for the second AL that runs at 110. If the data returns an error or null whatever, I don't run the second, bigger query. You can also have a third AL that pops the message you want.

HTH
Later
Stephen

Abdullah Baytops wrote:

**
I have created a SQL call inside an active link that is connecting to a remote database and bringing back information that is viewed in Remedy. I would like to end the active link if the conection to the remote databse is unavailable. How could I also either end the SQL call being processed in the Activelink and also display a message saying remote database unavailable?

20060125This posting was submitted with HTML in it




Find your next car at Yahoo! Canada Autos 20060125This posting was submitted with HTML in it

** I handle this a different way in that I have a process that runs every few minutes and tests for database connectivity. If the process cannot communicate with the external database then a flag is set on a form indicating the database is down and an eMail is sent to administrators. I have code before each SQL call that checks for this flag before running. If the flag is set to down I pop a message to the user letting them know. The process does something like attempting a connection to the external database that will timeout\fail quickly.

I used to do the simply query first, as Stephen mentioned, but found that Remedy would churn for almost two minutes until it realised the connection was lost. At that point it would tie up a dBase thread. 10 users trying this and the ARS server was hosed.

I also found the flag very handy in that I could easily shut off connection to an external database by setting the flag state to down manually. The application we have connects to 15 external Oracle databases.



On 2/2/06, Stephen Lumini wrote:

**
I don't know of anyway to "cancel" an AL once it has started, but when I have the situation you describe, I have a "test" AL that runs first.
So at 100 I have an AL that runs a count or some other real quick query to the same table and have it set a field - I use that field as the part of the qual for the second AL that runs at 110. If the data returns an error or null whatever, I don't run the second, bigger query. You can also have a third AL that pops the message you want.

HTH
Later
Stephen

Abdullah Baytops wrote:

**
I have created a SQL call inside an active link that is connecting to a remote database and bringing back information that is viewed in Remedy. I would like to end the active link if the conection to the remote databse is unavailable. How could I also either end the SQL call being processed in the Activelink and also display a message saying remote database unavailable?

20060125This posting was submitted with HTML in it








Find your next car at Yahoo! Canada Autos 20060125This posting was submitted with HTML in it






--
Frank Caruso
Specific Integration, Inc.
Senior Remedy Engineer
www.specificintegration.com
703-879-6465 20060125This posting was submitted with HTML in it