Home > Archive > Clarion > July 2004 > Killing a process on error
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Killing a process on error
|
|
| Peter Miller 2004-07-13, 3:55 pm |
| I would like to kill a process
I have an app that runs every 10 minutes
Pulls data from DB1 to DB2
My problem is that network problems occasionally stop communications
My app halts with the std Clarion error message - error xxx
I would like to intercept this call to the error manager and just shut
down the process
10 minutes later, my app should just try again
I have tried on error(), post(event:closewindow) at strategic points
in my app but still get the "communications error" message
PM
| |
| Andre Engelbrecht 2004-07-13, 3:55 pm |
| How about getting the file size of the source file. Then, after pulling the
data from the source file to a temporary location, verify that the two are
the same. If the sizes match, update your destination db. If not, delete the
temporary file
Andre
"Peter Miller" <peter.miller@fr.unisys.com> wrote in message
news:c633fabd.0407130651.6e94c76a@posting.google.com...
> I would like to kill a process
>
> I have an app that runs every 10 minutes
> Pulls data from DB1 to DB2
> My problem is that network problems occasionally stop communications
> My app halts with the std Clarion error message - error xxx
>
> I would like to intercept this call to the error manager and just shut
> down the process
> 10 minutes later, my app should just try again
>
> I have tried on error(), post(event:closewindow) at strategic points
> in my app but still get the "communications error" message
>
> PM
| |
| Peter Miller 2004-07-15, 8:55 am |
| The two DBs are MS SQL 2000 and SYBASE SQLanywhere
My app stops with an error screen if there are network problems -
about once per w
I need to trap the error and kill the process ( process template )
that is unable to complete because of the network problems
"Andre Engelbrecht" <fivetalents@telkomsa.net> wrote in message news:<cd0v68$7dl$1@ctb-nnrp2.saix.net>...[color=darkred]
> How about getting the file size of the source file. Then, after pulling the
> data from the source file to a temporary location, verify that the two are
> the same. If the sizes match, update your destination db. If not, delete the
> temporary file
>
> Andre
>
> "Peter Miller" <peter.miller@fr.unisys.com> wrote in message
> news:c633fabd.0407130651.6e94c76a@posting.google.com...
|
|
|
|
|