>>Exactly! and it does work without a hitch in debug, but not otherwise. I am running the code in a VFP window, mind, but still ...
>
>Hard to say then. But I definetely would not name the window Error (would at least name it wndError) and I would use SELECT 0 as Borislav suggested.
>
>But anyway, from the first glance this code should work as is, unless there is an error somewhere eaten by the error handler.

I agree. It's the code of the idiot who wrote this, selecting specific work areas. I have to have eyes in my butt to check everything I do doesn't have a knock-on effect elsewhere (he may "Select n" and "Use" somewhere else). It's a mine-field, I tell yer and, to mix metaphors, I have to walk on eggshells!