>>
>>George.
>>
>>Thanks for your reply.
>>
>>The problem is that when an error occurs in an object VFP always transfers control to the ERROR method of that object if it has code. Any ON ERROR commands in effect do not get consideration during this process. If the RETRY command is in the ERROR method the program goes into a tight endless loop of ERROR - RETRY - ERROR - RETRY etc..
>>
>>Am I missing something here? Do you have any other suggestions?
>
>Bret,
>
>I gotta stop messing around with FPW. Change the ON ERROR to SUSPEND in that program snippet. That will bring up the command window, from which you can activate the debugger with DEBUG. Use Step Into to execute the RETRY line and you'll be back at the command that caused the error. The RETRY will throw you back to the offending line of code, after which youcan cancel. Of course you'll have to place that snippet in the Error event that's connected with the object in question. That's about the best I can do.
>
>George

That did it George and we are sending you BRAVO ZULU's (translated our thanks, for you non-navy types) from naval surface warfare center.

Thanks again

Bret