Hi,
I have a legacy application that was originally writting in vfp 2.6 and then run under vfp6.0 and the app was running fine and had quite a few of the old @..Say and @ ... get statements. The customer was running win2k and then bought one new machine which XP and we got a lot of "Visual foxpro caused and exception ...." errors. So I figured we go to 9.0 and we did now all the screens work fine on the WIN2k Machine but on the XP you get the screen and all the @.Say and @,, GET areas are invisible. You can make them visible by clicking on them if you know where on the screen they are and then they behave as expected except that all the background colors are white.
So as it says to use the new screens instead I did a functional conversion of the 2.6 SCX and again it works great on the WIN2K machines but on the xp machine all objects disappear and only can be displayed when clicking on them.
A different app that was written from scratch in 9.0 works fine so is there anything that the "functional conversion" does (like setting certain properties) that cause those problems when run under XP. Ideally I'd like to run the app as is that was running under 6.0 as we want to just eliminate the crashes.
Any Ideas would be apprechiated
Visual FoxPro1
| 
