There must be something else going on in my system, but I don't know what yet. I had the problem again yesterday and the routine had a RETURN statement so I think we're right that it's something else.

I'll post here again if I get a solution or more info...

Any other ideas?????

Thanks,
Rick


>Hi, Richard-
>
>>Thanks for the information. I've checked and in my case I'm staying within the current module (trying to go back a few lines).
>
>So, the bug happens one one line in a method, and you are trying to set next statement to another line in the same method? You're not actually in an ON ERROR trap? Or in an Error method?
>
>What's the error you get?
>
>>So...even a form METHOD should have a RETURN?
>
>Yep. IMO.
>
>>IF a form METHOD doesn't have a RETURN the debugger may not give me the Set Next Statement?
>
>No, the RETURN doesn't have anything to do with whether Set Next Statement is available, so far as I know. But what it does for me is I'm guaranteed that I have a last line in the method to set a breakpoint on, or, when it works *g*, Set Next Statement to. If the error occurs on the last line of a method, and you leave RETURN implied, then there's no way to break within that same method.