Does the following work for you????

ON ERROR DoSomePrg()
...
PROCEDURE DoSomePrg
   ON ERROR
   ?? CHR(7)
   RETRY
ENDPROC

bear in mind that after this executes you will have to manually reset the ON ERROR before resuming the program and you've examined the problem.


>Thanks. Unfortunately, there is still the problemn of what line I get parked on after whatever program is invoked by ON ERROR.
>
>Jim
>
>>>Is there a way to create an audible notification when you get a bug in the development environment?
>>>
>>>I have a routine that runs for quite a while (20 minutes or so). While it is running, I move on to other things. If/when a bug occurs, I'd like to hear some audible notification, so that I don't have to keep checking all the time.
>>>
>>>I haven't gotten anything to work with ON ERROR (I thought I could call MESSAGEBOX), as I can't get the program to halt on the error line.
>>>
>>>Any suggestions, or am I barking up the wrong tree?
>>
>>Another way would be to have a function which would play a sound for you and call it from where you need it - something like
>>
>>

procedure RingABell()
>>if version(2)=2   && development only
>>??chr(7)
>>endif
>>return ""
>>

>>
>>You could call that function from any error event, Catch clause, or even
>>
>>

assert lEverythingOK message "something fishy here"+RingABell()