Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Unprintable Report Form
Message
De
02/12/1998 13:06:26
 
 
À
Tous
Information générale
Forum:
Visual FoxPro
Catégorie:
FoxPro 2.x
Titre:
Unprintable Report Form
Divers
Thread ID:
00163292
Message ID:
00163292
Vues:
67
I have a real poser which I hope someone can give me ideas about. It has been going on for about 2 months on different machines and essentially boils down to 1 of my report forms (qfax2.frx)will not print on a given machine (1 of 9 machines running the same compiled .exe, all identical and replaced daily from the subdirectory where I do my compiling). All other report forms print and fax(using Microsoft Fax on Fax through the Inbox) on this particular machine and all report forms including qfax2.frx print/fax on the other 8 machines. This has happened on 3 different machines at different times. First, a month ago, it happened on my bosses machine, Pentium 233mmx, Win98, HP520 printer. Next, about 2 weeks ago, it happened on another machine, 486DX80, Win95 release 1, HP672C printer. Now, last night, it happened on yet a different machine, Pentium 133, Win95OSR2, HP672C. In all cases it occurred right after a failure to fax. What transpires is, user selects the report option from a menu, identifies the record to print, the Win print prompt comes up (set printer to prompt command), a notification box "Opening Printer" flashes on the upper right of the screen, and another notification box opens in the middle of the screen "Printing qfax2" and then timeout. No error messages, nothing. I wait about 10 minutes (and normally it only takes about 3 seconds at most) before I "3 finger salute". The task menu comes up with "Microsoft FoxPro not responding". I close down.
I have recompiled the program, replaced the config.fpw, resource, and user files in the foxpro subdirectory essentially wiping everything out and replacing with new. I have reinstalled the print drivers after deleting and removing them. On the second machine I even reformatted the hard drive and reinstalled everything clean and fresh. On the first machine (my bosses), I gave up and a week later it cleared on its own. As this wasn't his primary function, it didn't hurt too much. However, the second machine was different, it was this employees primary function. This is the machine I reformatted the hard drive and started completely fresh to no avail. Again, after trying many different things over a period of 3 days, I was at wits end. On the 4th day, I turned on the computer (all computers are turned off at night using a main power switch on their strips so the power is off) and it worked. On each of these occasions, before giving up, I tried one last time and they still didn't work. Now I have another machine and it's doing the same thing.
I'm posting here in the event there is something somewhere in the file structure, header, etc. that I don't know about that might be trapping this form only and sending it somewhere else. I know that sounds off the wall, but all the logical steps have been taken to no avail.
All 9 machines are networked using Win95 peer to peer. Each machine is a self-contained client with all files and temp files contained on the client. The network is used to share the data files located on a single machine, my system, where resides the .dbf and .idx files only. As this is not a Novell or NT server system, there are really no individual settings other than the ones on the machines. I have tried turning off the print spooler, setting the printer port to SPP, ECP, EPP all with no effect. I have been in contact with HP who insists it is not the printer, Microsoft's support page which has no information to work from. I belong to the L.A. Fox user's group and have tried for help there, and they too are obviously stumped.
I apologize for the length of this but hope with this background, someone can give me some ideas as I've pretty much used up all of mine. My next course is to code the report form to a prg with @...say, @... get, etc. in the event it's something in the report generator. I'm not optimistic as everything has worked fine for almost a year until recently with no changes in the report form or the program that calls it. Additionally, there have been no upgrades or changes to the individual computers. I am really at a loss.
Thanks in advance for any help
Répondre
Fil
Voir

Click here to load this message in the networking platform