>>>>I've got a client for whom I created an EXE in VFP5. I will be installing the product in offices down the east coast of Florida, and I beta tested it in two separate
>>>>offices, fixed the bugs, and released it to a third office. This is where the fun began.
>>>>
>>>>There were some really strange problems (due likely to file corruption) which have been fixed. Now the product seems to be working well enough, but when the
>>>>user wants to print a form (an FRX populated with two related files and some memory variables), it prints the most bizarre characters--squares, some numbers
>>>>which look right but are printing in the wrong place, even a telling "BtnExit" on the form, which is the name of one of the objects on the screen. This form works in
>>>>the other two offices. Does anyone have a clue as to where to go with this?
>>>>
>>>>JR
>>>
>>>It looks like a corupted/wrong printer driver. try to reinstall your app and any printer drivers. Does it print ok in preview mode?
>>>
>>>Vlad
>>
>>Doesn't VFP take its driver from Windows? The printer works fine in other products. If it doesn't take its driver from Windows, should I reinstall the library file? Remake set-up disks & do the whole thing?
>>
>>JR
>
>Is it so difficult?
>
>Vlad

There have been several messages in the last month or so about VFP Reports using the printer they were DESIGNED on instead of the Windows Default. You can fix this by removing the information saved in the FRX/FRT files.

MAKE A BACKUP of one report, then take the printer information out of field TAG and TAG2, first record, I think, and try it again. Since your reports are compiled in, you may want to fix up a quick EXE with un-compiled reports for testing at the remote client.

If this works, fix each report and re-compile your EXE so all clients have the non-specific reports.

HTH
Barbara Paltiel