I a couple of months ago my workstation was changed to a Win98 SE. A short time after that the SP#4 was installed.
Now small failures are beginning to happen. Code that hasn't changed in a couple years is barfing a lung.
A pgm containing the rft control, when recompiled and the setup wizard run, produced a package in which the rtf control
refused to be registered. (It was a simple program to create a VFP runtime install kit).

In another situation: CASE cTmp == ALLTRIM(cVar) failed with a system error in the EXE, but the dev mode and the debugger on the EXE both ran ok. When I removed the ALLTRIM from the CASE statement and trimmed before the CASE statement the problem went away,
CASE cTmp == cVar worked..

A similar situation occured with INLIST(cVar1, ALLTRIM(cVar2), ALLTRIM(cVar3)). Same diagnostics as above.
I switched to an AT() code and recompiled. That cleared it.

In another situation, a program mis-tested an IF nVar1 = nVar2 construct and took the ELSE condition even though both
vars were numbers and they were EQUAL!!!. (You know how the debugger puts quotes around strings but not around numbes.
The vartype tested "N" in the debugger too. That's when I decided to reinstall VFP and SP#4.
I'll let folks know how it turned out.
JLK



>>Now that u mention it, many times is when I'm doing something related with reports. Some times after a print command from the print preview, some other time in the second attempt to execute a report. But mostly it's a random problem.
>
>Try changing the printer and video drivers to generic drivers.