I think that you are looking for a lot of trouble and wasted time trying to migrate a FPW 2.6 to VFP 9. I've succeeded once in making a FPW 2.6 application run in a VFP 3 environment and the result was so ugly (in screen and in code) that I killed the idea of migration.

My advise is forget it. Rewrite the whole thing. If you choose the path to a complete rewrite, I wouldn't go with VFP 9, unless you plan a second rewriting in a couple of years.

>I have a large legacy application written in FPW 2.6 we are trying to migrate it to the VFP9 environment.
>
>We have do decided to do use a hybrid conversion strategy. Run the old code (from the SPRs generated by FPW) and add new functionality using the VFP.
>
>The problem is that the FPW foundation READ required by the FPW code is not allowing the VFP screens to fire their events – essentially the Read Events is being ignored.
>
>The program is structured something like this:
>
>a) Main program calls the menu (main.mpr) followed by a READ VALID()
>b) From the menu – call the SPRs as required – they run – no problem
>c) From the menu - DO FORM VFP_FORM - problem.
> Whenever I click on the screen, the program immediately jumps to the foundation Read’s valid function
>
>I have tried to :
>a) issue a READ EVENTS immediately after the DO FORM command and it is ignored.
>b) Issue a READ EVENTS before the foundation Read – the VFP code works but the SPR code that requires the foundation read fails.
>c)There is no difference between modal screens and non-modal screens.
>
>Any assistance would be greatly appreciated.