Ok, I started playing with this, and I've obviously reached brain cramp... what is the easiest way to do a hex dump of an @...say report in VFP? I must be missing something...the only way I can see is to dump it to a text file and then read the file in character by character checking the hex value of every character?

>It's tedious, but the hex dump will tell you exactly what is being sent. Try it with a small report if possible. Count your 0D/0A pairs up till your FF. Any extras should point to exactly where the problem is. I really don't think it's the drivers. I know, works in FPD but the fact that hundreds work and these 3 don't points to the report IMHO.
>
>>Hi Jim,
>>
>>I've reset the printer to its default settings so many times it's ridiculous. I've manually set the TOF and the form tear-off to no avail. I've tried the Oki ML 320 Elite (IBM), the Okidata ML 320 IBM, the Okidata ML 320/T, etc. I've downloaded all drivers from Okidata for testing purposes and tried both Windows builtin Okidata drivers. What is strange is that hundreds of @...say reports print with no problem and these problematic reports print fine in the FPD26 version of the app using the same code (but not using the windows printer drivers of course). I'm testing printing to a file now...
>>