Here's a strange one. This only happens on a few (3 so far) of hundreds of reports printed using @...say to an Okidata ML 320 Turbo printer in VFP8 or VFP7. I have stepped through the reports that are having this problem starting with printing only the first line in the report and continuing by each time printing one more line to try to determine what if anything is causing this problem to no avail. I have manually typed the program line by line into a new .prg even. The problem that is occuring is that when the eject is issued when finished printing the @...say reports to an Okidata ML 320 Turbo printer the page ejects too far by approximately 2 lines. Whether or not forms tear off is turned on makes no difference. If forms tear off is turned off, then the printhead ends up 2 lines too far down the same as with forms tear off turned on. (The 2 lines are too far down respective of where the printhead should be in either case) I have tried using different (I've tried all of them now) printer drivers using both of Windows drivers and all of Okidata's drivers. This is happening in all versions of Windows so far. What is strange is that similar reports using @...say feed correctly. I have also tried stepping through the line numbers on the paper until I reach 66 and then issuing a printer reset code there instead of using the eject command to no avail even. codes sent to the printer are sent using ???. Codes typically sent are the font pitch, the lines per inch, then the @...say report is printed, then a 10cpi command is sent to the printer and then a printer reset code. This works in literally hundreds of reports successfully, but a few are exhibiting this 'creeping' problem. I have tried printing the report with no commands being sent to the printer and in these reports it still occurs. I have not been able to isolate a single line of code where it is actually causing this problem to post anything so I am hoping someone has seen behavior similar to this and knows of a resolution.

Anyone have any ideas? Seen this before?

TIA,
Tracy