Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Windows 2000 and VFP6.0

Status
Not open for further replies.

RTorrance

Programmer
Apr 12, 2002
64
CA
I have kind of a weird situation. I have a user who is running Win2000 originally with no services packs. (Now has service pack 3) When this user tried to run my application, it would run fine until it was about to display a report, then would close the whole application. This only happened on 2 out of the 4 different reports that they can choose from. This application works fine on all other users computers running Win2000 or WinNT4.0. If anyone has ever seen this before or has any suggestions, your help is greatly appreciated.
Thanks
 
Honestly, no idea.

You need to narrow down the problem.

My instincts say printer drivers - can you put a PDF creator on the problem machine?

If not, add a local driver for an HP laserjet IIIP and set it to go to a file.

This is almost a generic printer and is good for most things - so it should cause no problems.

try again and get back to us here at Tek-tips.


Regards

Griff
Keep [Smile]ing
 
Also, What causes VFP to exit?

That is, does it just disappear, or does it show an error first?

If it shows an error first, who is showing the error? Your program's ON ERROR routine, or VFP's internal Exception handler, or Windows trapping an Unhandled Exception?

What is the text of the error?
 
The report does not go directly to the printer but preview in screen first. It does not show an error message, just closes foxpro.
 
Try uninstalling and reinstalling your foxpro application. Sometimes that helps. I've seen foxpro do some pretty strange things...
 
The Print Preview still uses the "bad" printer drivers, so whether you print or preview the error can happen - you might want to try the fixup code.

Rick
 
Thanks for your input. I'll try the drivers and let you know how it works out.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top