>Thanks Bill
>
>Yes I know that I cannot ship the compiler or IDE. What I have subsequently found out is that they have shipped the dev environment of every release of FoxPro since the DOS product...However my concern right now is that I need to stop the VFP stuff going out. That's why I made comments about public domain access and the like on old, unsupported tools.
>
>As you will see in my reply to Wayne, one of the categories of errors is with printer drivers causing problems. One of the senior developers here (the one who decided to do the functional conversion (!)), has found that installing the VFP6 dev environment on a testing machine appears to reduce or fix completely these issues. That's where this idea has come from.
>
>So I'm between a rock and a hard place in some ways...
>
>Regards
>Simon

Printer drivers ?
bah - in the past I always had two versions of a report.
ONE for an HP laserjet, and another for an Epson compatible dot matrix.
Always used the HP LJ III pcl 5e version for dev work.
Then when my apps installed - they set up that printer driver with a particular named printer. Then my app would chose that named printer to print to.

OTOH - you may be experiencing issues with the contents of the expr, expr2 and that 3rd column in record one of the report itself - I usually strip those out.