(These all get compiled into a single exe file.) We are in the process of converting the application to. While it would be nice to do as you suggest with respect to including the "Set Printer TO." command, there are almost a dozen different labels that are being printed with print commands scattered in almost 40 different prg files. the label forms were created a couple of years ago by a different programmer, and the "save printer environment" WAS checked by him. So far, re-doing the label form to incorporate the newer model label printer number sounds like what I'll try doing next. I can remotely "see" the list of printers in their Windows "Printers and Faxes" window, but it would be good to get the names that the Foxpro application would see on their machines. Again, the users don't have VFP installed on their PC's, and the nearest user is about 40 miles away from mile location. Thanks for the suggestion of trying the ?getprinter command. Yes, I understand that when developing new Foxpro applications, these suggestions should usually be followed, but again this is dealing with a legacy application to print prompt", or "set report behavior.". I cannot make changes in any prg file, so I cannot use suggestions which involve program commands, such as "report form. they don't even have Foxpro installed on their machines. but please note that the end users are running an compiledc executable. Thanks.Īgain, thanks to everyone for taking the time to make suggestions. any hints or reports of similar problems would be helpful. I'm researching this along a number of different lines. My QUESTION: Any suggestions as to what might be causing the printer to stop working? Could there be some remnants of the Model 220 driver buried somewhere in the registry that, depending upon some other programs being run by the user, could somehow corrupt the Model 240 printer driver? Would the problem be permanently eliminated by just re-doing the Label forms using the newer model printer? Why would having to keep re-installing the driver be necessary? This working period could last anywhere from several hours to several weeks. The print job was correctly being routed to the label printer, even though it was not the default printer.) The problem could be resolved by re-installing the Model 240 printer drivers, and the label printer would again start working until the next time it started giving errors. the printer icon in the windows tray would just display a red question mark/trouble overlay, and the print job would just hang with this error indication. However, after some time of use, the label printer would quit working and the user would receive a printer error when they tried to print labels. Most of the time, this renaming trick worked with no problem, and the labels would print out on the Model 240, even though the Foxpro label template file had been created with the Model 220. When the users installed this newer model printer, they were smart enough to understand that after they installed the model 240, they had to rename the printer in the Windows printer list to be "Smart Label Printer Pro/220" rather than allow its normal installed name of "Smart Label Printer Model 240". Over time, several of the users had swapped their SLP Pro/220 label printers with SLP model 240 label printers. The label printers are hooked up as local printers (but not the default printers) on the users' PC's. The labels were designed using a Smart Label Printer Pro/220. (All of the users are running the application on Win XP SP2 machines.) LBT files that the Foxpro label designer creates. It creates several different types of labels using the standard. I've inherited a Visual Fox Pro application (originally written in Foxpro for Windows, but more recently compiled with VFP 7 and then VFP 9).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |