I have a simple screen in FPW2.6. It has some startup code that computes numbers to memory variables. And then on the screen it either SAYs or GETs those values, along with a few labels. And it has a few buttons which respond to activities.

What's happening is one of the GETs is inputting a value, but on 32-bit Win7 machines, sometimes, when the user presses Enter to leave the data as it is, it resets the field contents to 0.00. Using TAB instead of Enter always leaves the value as it is.

Here's the code:


Several developers are at a loss to explain this behavior. Does anybody have any ideas to try?

Thank you in advance.

Best regards,
Rick C. Hodgin

The screen works correctly on 64-bit Win7. And I have a virtual machine running 32-bit Win7 (on 64-bit Win7) that does work correctly on/under as well.

It's the sporadic nature that is causing the concern.

There is a hidden form at this time in execution which has a timer that fires 3 times per second. All of its variables are declared LOCAL, and it doesn't use any of the same named variables, tables, or anything. It is a background form which hides itself when other things are happening on the system, and when the system is otherwise idle, it brings itself back as a top-level "what to do" kind of form.

Best regards,
Rick C. Hodgin

I guess I should say make it very clear that this issue is in VFP9. The screen works properly in 2.6. And it works properly in VFP9 on 64-bit Win7 machines. Only on 32-bit Win7 VFP9 does this issue exist, and even then only from time to time.

Best regards,
Rick C. Hodgin

Is everything else also the same? Are the same VFP9 runtimes installed, with the same SP version? And where?

Bye, Olaf.

That's a good question. I had assumed so since the company I'm researching this for builds their own installer which is pushed out to several hundred clients. However, it might not be. Will check into that.

Best regards,
Rick C. Hodgin