Generic / Text Only Driver does not work through CRVS2010 Runtime?

[#1]

I am having trouble printing to a Cypress printer. The Cypress printer uses the Microsoft Generic / Text Only Driver. The issue is that if I preview and print the report via the Crystal Reports for Visual Studio 2010 IDE in Visual Studio, the special Cypress codes print perfectly to the printer. If I run the same report through the CR for VS2010 runtime and do a PrintToPrinter, the codes get complete garbled and ruined. I am doing no formatting through the runtime, simply loading the report and then printing it directly. This issue does not happen with other printers (e.g. HP, Brother, etc).

Sample Cypress Codes:

^{form = TEST_FORM}

^{var note = "This is a note"}

Sample Print From VS2010 IDE to File (or printer):

^{form = TEST_FORM}

^{var note = "This is a note"}

Sample Print FROM Runtime:

^{for=SmEST_FORM}

^{var n=Tohei = "This is a }note"

Sample Print to file from Runtime using Generic/Text Only:

^{for

=m

T

EST_FORM}

^{var n

=o

T

t

"h

ei

s is

"a note

Does anyone have any suggestions? It works perfectly from the IDE, but fails every time from the runtime. Thanks!

Kyle

[former_member200290]

If this was demonstrated in other printer drivers we could definitely look at this as an issue, if it only happens with one particular printer driver, then the odds of this being our issue is pretty slim.

We use the printer driver to lay out the report, the metrics we get from the printer can cause line feeds if the text is no longer able to fit on the same line in the text box.

The problem is that if we go ahead and track this as an issue it will be a lower priority unless we can duplicate this with another printer. If we can confirmed that it is our issue it may be looked at by our developers. However this does not mean the printer driver is going to recognize what we send as the escape codes, after it is fixed. Nothing we print should be picked up by the printer driver as a code, and stripped, if it does this is considered incorrect behaviour on our part, and should be fixed so the printer no longer recognizes them.

Trevor