Is the program FPD dos? The program is not DOS based, it is FoxPro 2.6 (we made modifications to the config.fpw file to no avail)

Is the environment the same? Yes, in researching the problem we were able to recreate it when the .exe was ran from within FoxPro and when it was simply executed. But the environment is the same.

Is there a config.sys or is it windows 2000/xp? Windows XP Platform on all machines (no custom config file in the OS)

Is the printer connected the same on all machines, is it the same printer and printr driver, and is the local lpt port on the workstation mapped if it is a shared network printer? Same printer, same drivers, mapped over TCP/IP.

We were actually able to solve the issue without true resolve by uninstalling one of the machine's printer driver and reinstalling THE SAME DRIVER and the report is now able to print.



>Is the program FPD dos? If so, it would use config.fp not config.fpw. Is the environment the same? #of files, buffers, etc? Is there a config.sys or is it windows 2000/xp? If so, what is in the config.nt file or does your shortcut run a custom config file (in the os)? Is the printer connected the same on all machines, is it the same printer and printr driver, and is the local lpt port on the workstation mapped if it is a shared network printer? If a shared network printer is used, is the share name 8 characters or less with NO spaces?
>
>>Greetings Programmers.
>>
>>My name is Jason and I am having some issues with printing a report in FoxPro 2.6. We have a billing card that prints on non-standard paper to a laser printer that recently freezes up on the FoxPro environment "Printing" window. Other reports that we print are nearly identical to the one that freezes, except the file name is one or two characters off.
>>
>>I have tried using 4 different computers to run the application and 1 of those consisently freeze on that one report. Using the same dataset (customer A) on another machine it does not freeze on the routine that prints the report.
>>
>>I am fairly confident that the config.fpw is the same (will double check that this afternoon).
>>
>>Another wierd issue along the same lines: Using another customer's data (customer B), on two machines with identical config.fpw files, one is able to print the report with no worries, the other freezes at the FoxPro printing window. The wierd part is that when the computer that froze on the report with Customer B does not freeze when printing the same report with Customer A's data...
>>
>>I am racking my brain over this one, so any help would be greatly appreciated!
>>
>>Thank you in advance.