Ok, It seems the SQLEXEC does not fire the current ON ERROR routine.
Just fixing up the application for Oracle Cluster Servers and when a server dies an error will be reported in the application that I need to trap and
then recconect (then it will route me to the next server.) Problem is I wrote. SQLEXEC() all over the place.

I suppose I could write a function...

FUNCTION EXECUTESQL
LPARAMETERS lnHandle,lcSQL,lcCursor

But the problem is the Bind Variables become out of scope for example in this piece of code:

LOCAL lcDB

lcDB='STYLES'
SQLEXEC(ConnHandle,'update styles set db=?lcDB','mytable')

Again I could find all the bind variables anywhere and make them PRIVATE
but that is an error prone job.

Is there anyway you can get the ON ERROR or form error to fire when
SQLEXEC() returns an error?