Continuing the saga of the dissappearing form, I went on to continue writing the program with a Timer class.

Since I needed one textfield to show the DateTime, I used "Set Sysformat On" in the INIT of the form to let the user see the date & time started as set under Windows Environment. To test the timer out, I placed another TextBox to show the current time, controlled by Timer set at 60,000 intervals (i.e. 1 minute). Happily, I compiled into EXE.

As the GoodBook (i.e. VFP) says, Timer is not exact or accurate, so I took it as gospel truth. So when I ran the EXE, the CurrentDateTime controlled by Timer didn't update exactly on time. I sort of expected it but when it decides to only update whenever there is some activity on the screen, eh! what's that? Not only that, it hangs the system clock also. SO I let the screen sit quitely by itself for over 5 minutes and still the CurrentDateTime is not updated by Timer. Then I doubleclick the system clock and saw that it hang unless I move my mouse, then it jump to current time and then stop again until I move my mouse again.

Hmmm... This problem has got to be between VFP and Windows, but what?

Then I remembered that I place "Set Sysformat On" in the INIT of the form. Whatif I remove it? You know the rest of the story.

Anymore crazy stories of the TimerZone?