I agree with Rob. The default path is changing and you need to code for it.
Tracy -----Original Message----- From: Rob Anderson Sent: Thursday, July 16, 2009 10:02 AM It is changing the default path I think. Preserve it before calling the print routine, and then restore the path afterwards. HTH, Robbo. Rob Anderson | Development Team Leader | Pegasus, an Infor company | Tel: +44 (0)1536 495006 | Fax: +44 (0)1536 495214 | Mobile: +44 (0)7917 +615401 | www.pegasus.co.uk -----Original Message----- From: Kurt Wendt Sent: 16 July 2009 14:57 Hey there folks, One of our clients is having a strange problem with our FoxPro system - although its not specifically a problem with VFP - but rather with PDF file creation. Although, the problem IS causing VFP to Crash and close when the problem occurs. For any kind of report or printed output - the problem is occurring. When they go to print something - if they chose to print to a printer (or even select a print Preview option) - the problem does NOT occur. However, if they choose to print to a PDF file - after they select WHERE to save the PDF file, and after a brief period of time (as though the PDF file processing is occurring in the background) - instead of properly returning control BACK to VFP it Crashes! Each of the crashes give an error saying it could not find a file - whether it's a DBF file (which of course IS there) or some other file. It just seems that when the location of the file is being selected - its as though the FoxPro default path is being changed - and then it totally messes up FoxPro upon return from the PDF creation. Additionally, as part of the testing that my Tech here was doing - he even selected creating the file in the root folder of the VFP system on our client's system - and that DID stop the problem from occurring. And, yet, if I run one of our other clients systems locally here (and in each case we are running an EXE compiled in VFP7 - as opposed to an APP file) in its test folder - and I generate a PDF file (and specifically tell it to save the PDF file to my local C: drive and not a location on the server where the system resides) - I do NOT get this error. Needless to say - I can't recreate this error locally so I can look into it a bit more - as it ONLY happens directly on the clients site and our Tech can recreate the problem when they remotely log on! Hopefully someone has a clue - which hopefully will NOT require that I do an extensive programming change across their system! TIA, Kurt _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/000f01ca061f$a9682cd0$fc3886...@com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
