Harry,

This is a VPM problem, at least up to Version 6.0, and maybe afterward. Because of VPM's READ EVENTS and the fact that you are in their compiled app, and not in VFP itself, many of the features of VFP's IDE are not available. "VPM giveth, and VPM taketh away." One of the things that eventually drove me away from VPM.

Go back and scan the VPM Developers newsgroup. In any given week in 1998 you will find long conversations between Hank Fay, myself and others about how VPM taking things away from us.

>>Maybe you could email your form and it could be tested by others....
>
>>I'd be glad to test it out for you.
>
>Hello Michael and thanks for the reply.
>
>Unfortunately its not "a" form problem. Its "any" form. Its a vfp problem. If I go into any form in the form designer, enter any method and try to do a search or replace within that method, the form bombs out as described in my previous. This includes brand new forms with no amendments which I generate just for the purpose of testing this behaviour. Previous suggestions included killing any foxuser files - which I've done repeatedly (last night I carefully removed about 20 foxuser files scattered about my c drive to ensure that it couldn't read any of them). I've also deinstalled and reinstalled vfp, vpm and sp3 completely twice with no effect. I've also tried various default setting and setting "resource off".
>
>Harry