There are several reasons for this, including your use of macros (could have something to do with file locations as many of these utilities, and many parts of gs, aren't particularly fond of spaces in the path) <s>.

A lot of people don't understand how to do this properly, especially since the pathing and class-finding mechanism is somewhat alien to Windows users -- it takes a lot of work to get everything in the right relationship.

Another possibility is that you are not embedding the right fonts.

I took care of much of this in my pdflistener class -- or pdfclass, if you aren't working in VFP 9 (since I've been using Ghostscript since Fox 2.x <g>).

Some addtl thoughts:

* -- My class lets you set the driver that it uses (and transparently installs, if necessary) but FWIW I would not use the generic one.

* -- My class also (of course) #DEFINEs all the messages with _LOCs and believe me there is no OS-language specific reason why this technique will not work. People use it all over the world.

* -- Quality is not a problem -- in fact somebody wrote to me today asking could he LOWER the quality of the output since it's very high-res and he would prefer it take less time to print the PDF <g>. (The res is a function of the printer driver settings and the command line for GS, FWIW)

>L<