Forms 3.0 and Control-C

We are running an Oracle (V7.0.16) forms(3.0) application that contains user-exits (writtin in Pro*C V1.6) on a Sun platform (server OS:4.1.3, client OS:4.1.1).

Our GUI wrapper is formstool (V2.0.0.2.3: yes, I know it is no longer supported but we have not been able to upgrade yet and our clients require a GUI interface -- no matter now primitive).

There is no problem running the V3 forms inside the formstool wrapper.

My question is our users have a tendency to use Control-C to "cancel" long running queries (and I am assuming long running commits). What does the Control-C do to forms? It is not specified in the oraterm file for the application so I would assume that it is passed through somehow. What affect would this have on the user-exits? They are currently experiancing some "dissconnects" from the database. What I am trying to determine is if the Control-C scenario is a contributing factor to this problem or another problem entirely.

I am thinking of adding in the Control-C to the oraterm.r file and mapping it to the [exit/cancel] functionality. What are the pros and cons to this?

Any information, suggestions, hints, comments, etc. would be greatly appreciated.

Ken Niedermeyer.

--
---
Ken Niedermeyer			| The views expressed above do not represent
Computing Systems Analyst	| those of my employer.... (but when do they?)


                                | 

                                | NOTICE:


Internet:                       | Lack of planning on your part
kan9691_at_eeidf002.ca.boeing.com  | does not constitute an emergency on my part.