I know that the code executing has this line in it "set reportbehavior 90" and that it was compiled under vfp9. The coverage file made in VFP 7 development environment shows that the line actually executes - 0.000099,myprint,myprint.printitem,2,c:\vfpcomm\printing.vct,6 - this is the line set reportbehavior 90.
The only thing I can think of is that the runtime is "trained" to ignore "set" commands that it does not recognize.
A problem is a problem only as long as it has a possible solution. Lacking that, it becomes a FACT!