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 Member]

Don Williams solution to use the RAS works. However, with COM Interop registration issues for the CR2010 32-bit runtime, it is not a viable solution that can be redistributed to users.

[former_member11696]

If it works in DEV then it will work for distribution. Check your Microsoft help file on how to distribute runtime.

[Former Member]

I concur with Don. Search these forums, use the search box in the top right corner of this web page. The solution is here. If you don't find anything that helps you, create a new thread. Remember the [rules of engagement|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagemen]; one issue per thread.

- Ludek

[former_member200290]

As Don has mentioned for this new issue we need to work on a new thread.

However I do want to have a clear warning here that printer codes/printer escape codes have not been supported in our product since version 7 or 8 due to the way we changed our printing.

If you get this working we cannot guarantee that it will continue to work, as technically this is incorrect behaviour.

Kind Regards,

Trevor

[Former Member]

Trevor,

The escape codes may not be supported, but do text fields with text in them count as actual escape codes? From what I can tell, the codes are simply text fields in the reports at the top of the document. The fields are picked up by the Cypress Imaging system and stripped from the print document.

E.g. Cypress sees this: ^{FORM=MyForm} and strips this code off and overlays an image onto the print based on "MyForm".

The issue is that when using the Microsoft Generic / Text Only printer, the equal symbol in Crystal forces a line break, even though there is no linebreak in the text object. Depending on the font, a number of line breaks could be generated (Arial is particularly bad, Courier is only a single break). This seems to be a bug in the rendering engine when printing. Thanks.