We are using Visual Studio 2005 and 2008, sending a Crystal Report with embedded codes (in a native printer font - Courier) to a RightFax printer (server). Visual Studio 2003 works; this process stopped working (the embedded codes aren't recognized) when we upgraded to Visual Studio 2005, and then 2008.

With Visual Studio 2003, we use the Crystal merge modules (version 10.2.3600) included with the studio. They work.

With Visual Studio 2005, we use the Crystal merge modules from CrystalReportsRedist2005_x86.msm. They fail.

With Visual Studio 2008, we use the Crystal merge modules included with the studio. They fail.

Our RightFax server is currently running RightFax version

The problem appears to be the embedded codes (i.e. ):

when writing to a paused RightFax printer Q, in Windows XP spk2, the temp document file doesn't have the codes in it (they're part of the image, not separate - machine readable characters - like they should be). When released, the document shows up in our RightFax Q with errors.

Determining which of the 3 components is at fault is complex: Microsoft, Crystal Decisions, or RightFax - take your pick.

Anyone have any ideas on how to resolve this issue?

Any help will be greatly appreciated.

Thanks, Tom