>>ROFL, yeah, that one bit me a few months back. Hard as I have tried, I have yet to come up with Universal Error Handler. Too many things I want to handle in a custom manner, such as 1429 and 1884 errors.
>>
>>
>>>Anybody else ignoring Error 1001 "Feature not available"?
>>>My apps log it, but don't show the user something. So if I forgot to remove a SET STEP ON, I'll get 2000 messages in the log before I notice.
>
> I thought it is simple...
> We usually open compiled EXE file in the simple editor (like FAR, for example), search for string 'SET STE' and note all places where it exist. Than fix code and recompile. Same for other commands. So final appllication never have this error.
Could be a nice VFP option for lazy programmers - to have SET STEP ON automatically ignored in EXE. :)
Nick Neklioudov
Universal Thread Consultant
3 times Microsoft MVP - Visual FoxPro
"I have not failed. I've just found 10,000 ways that don't work." - Thomas Edison