>>>I recently converted a VFP3.0b accounting application to VFP5/SQL Server. Client using the same HP Laserjet 4 Plus to print their checks. New version of the app seems to handle the conversation with the printer differently. The output font is really large and they sometimes get error "detail band too large'. Determined that the user must always set properties on the printer back to default before printing the job. I am wondering if anyone has experienced something like this going from VFP3 to VFP5 with HP printer. I don't know if there is something I need to do in the .frx. I also wonder how VFP5 is different in this than VFP3.
>>
>>
>>I may be totaly off but...
>>
>>When you have printing problems with Reports a good Trouble shooting idea is to look in the FRX. Just open the FRX as a table and in the first record (should be) look in the fields. Make sure the printer model stored is the printer you are currently working with. Sometimes VFP will store the wrong printer model in the FRX. It is a good start when all else fails.
>>
>>HTH,
>>Tom
>
>I checked the .frx and the model was right. The properties for resolution and true type fonts were not what I wanted. Changed them and sent program to client (running WIN95). The behavior is as follows: If I launch my program and then change the printer to the desired printer, the properties I need are not the ones in my .frx. If I change them before printing, the report is still wrong. If the printer is the WIN95 default printer before launching my program, the report works right, the properties are right. The properties have already been set on the printer. Seems to ignore any settings in my .frx. Is there something I can do in my program to override this situation?
As a rule of thumb (FWIW), I delete the Printer setting in the FRX record in the first row (if you do this make sure you make a BU copy first! (s)). That seems to eliminate many problems since there is no info for VFP to use to setup the printer. It 'seems' to make VFP handle a printer in a more 'generic' sense.
My 2 cents...
Tom
