Search results for query: *

Olaf: -- that is exactly what I did -- put _screen.themes = .f. at the very first thing in app. Did not know about 2700. -- am running SP2. -- running into the (I'll call it a bug) with the @SAY clear problem was a real show stopper for this particular app since it is...

WhooHooo -- Problem solved by workaround as follows: Instead of writing the @SAYs within an activated window, I wrote the @SAYs directly to the screen via a WHEN() clause from a browse statement within a defined window. Cause of the initial buggy behavior was the "_SCREEN.THEMES" command...

Thanks for all the feedback -- I am getting more frustrated with this VFP thing as time goes on -- now I find that VFP7 is really not compatible with Win7 -- while it loaded and ran fine on the app after I initially installed VFP7, it failed to load after a Win7 reboot. Right clicking on the...

Tamar: From a post you made elsewhere (thanks a bunch) I already did the _screen.Themes=.F. and enginebehavior70 trick to eliminate other bad behaviors in VFP9 that made my nerves tingle (not to mention losing 20 or so hours of time dealing with "M$'s enhancements". Bottom line is that I plan...

My thoughts: "IF IT AIN'T BROKE, DON'T FIX IT

Thanks for the thoughtful feedback folks -- I hear what you say about getting into the 21st century -- given that, it will not be with VFP since MS has decided to make it "History"

The following code snippet runs fine in both VFP7 and 9 on initial load of VFP. With a more complex set of @ says (my real app) and other upfront code, the @say strings (e.g., "sdlkjlsdkflsdjflsdj") get cleared as soon as the brow screen is activated -- but only on the first load of VFP9 --...

Weird behavior in VFP9 (works fine in 7). Text written (@say) to screen gets cleared when browse screen is displayed in a new window. Only happens when VFP9 is first started and routine is run the first time. Subsequent execution of the same routine the text display does not get cleared.