Thanks Christof for responding.

>The problem is the ScreenHook stuff. This is not really supposed to work, even though it made it unfortunately into the VFP documentation. If you use VFP 8, you can use BINDEVENTS() to bind to _Screen events.

No I am using VFP6. This error was not generated in the EXE of the app but in the VFP env. after the execution is completed if I try to open any class VFP makes the bums rush.

So I guess once I get it up to the marks, I don't need this facility, so no errors and the user will love this and not have errors, fair deal, unless there are any pitfalls to this on the users machine.