Fritters
asked on
Printer not found
Using a product called Very PDFCamp printer driver. Print to that and a Save dialog opens similar to Adobe's printer driver. More options however. Anyway, now an older Foxpro application that always used to be able to print to this driver under XP Pro returns a "printer not found" error. When I use the select printer option under Foxpro, I "see" and can select that as the default printer (or the printer for just that print job.). However, the error occurs each time. I must have something to do with how Vista handles its printers differently than XP. Any ideas that I can try?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Get CutePDF for free http://www.cutepdf.com/Products/CutePDF/writer.asp
Vista supported.
Make sure when you print, you CHOOSE the pdf printer not another printer installed/default.
Vista handles the same, just need vista drivers for your printer.
Vista supported.
Make sure when you print, you CHOOSE the pdf printer not another printer installed/default.
Vista handles the same, just need vista drivers for your printer.
Microsoft has mentioned Foxpro 9 to be the only version 100% compatible in Vista, other versions are not
http://msdn.microsoft.com/en-us/vfoxpro/bb330856.aspx
http://msdn.microsoft.com/en-us/vfoxpro/bb330856.aspx
ASKER
CutePDF only gives the option to overwrite if the named PDF already exists.
PrimoPDF gives the option to append to a preexisting PDF, which is half of what I need.
Very PDF's PDFCamp (when it worked!) gives the option of Insert as first page and append. I need both.
My gut tells me that this should be a "simple" situation. So far no help from the developer of PDFCamp.
Any more suggestions?
PrimoPDF gives the option to append to a preexisting PDF, which is half of what I need.
Very PDF's PDFCamp (when it worked!) gives the option of Insert as first page and append. I need both.
My gut tells me that this should be a "simple" situation. So far no help from the developer of PDFCamp.
Any more suggestions?
PDF camp works in any other program like word, notepad, word perfect, etc with no issues right? Only with fox pro you are experiencing this issue? Could you try right clicking on foxpro icon and choose xp or 2000 under the 'compatibility' tab.
ASKER
Nope. Still the same problem. "printer not ready" when printing to the PDFCamp printer driver.
If thats foxpro using dos in anyway, take a look here http://www.tek-tips.com/viewthread.cfm?qid=1345881&page=7
Oh, so you can print to a normal printer from foxpro and any other application, But when choosing pdfcamp driver you are getting the not ready driver?
ASKER
>>Oh, so you can print to a normal printer from foxpro and any other application, But when choosing pdfcamp driver you are getting the not ready driver?>>
Correct
Correct
Are you using very pdfcamp latest version 2.3? http://www.verypdf.com/pdfcamp/pdfcamp.htm
And a very dumb question, if you go into control panel, printers, is the printer enabled or disabled? Right click on the pdf printer and you can enable/disable.
And a very dumb question, if you go into control panel, printers, is the printer enabled or disabled? Right click on the pdf printer and you can enable/disable.
also, download the autopatcher utility "apup" from www.autopatcher.com, and update the updater.
then apply all the patches applicable for vista to bring your system up to date.
you basically have a compatibility issue between the PDF printer driver and your foxpro version.
if you can, upgrade your foxpro to Visual FoxPro 9.0.
that ought to solve your problems.
cheers!
hathehariken.
then apply all the patches applicable for vista to bring your system up to date.
you basically have a compatibility issue between the PDF printer driver and your foxpro version.
if you can, upgrade your foxpro to Visual FoxPro 9.0.
that ought to solve your problems.
cheers!
hathehariken.
Yes, printers are handled differently in Vista and even newer applications and printer drives have problems which are solved continuously but slowly...
You have several options:
1) I would recommend to try XP compatibility box in Windows 7
2) Ask PDFCamp vendor for solution
3) You may ask somebody who is able do trace Windows in debugger to look what system component returns the Printer not ready status to FoxPro and do some work around
You have several options:
1) I would recommend to try XP compatibility box in Windows 7
2) Ask PDFCamp vendor for solution
3) You may ask somebody who is able do trace Windows in debugger to look what system component returns the Printer not ready status to FoxPro and do some work around
pcelba
XP compatibilty mode has been recommended and author is using Vista not win 7.
Author is checking with development at PDFcamp
All printers work, and can print to a normal physical printer via foxpro.
I asked to check if the pdfprinter was enabled/disabled.. haven't heard anything back, hopefully it was that.
XP compatibilty mode has been recommended and author is using Vista not win 7.
Author is checking with development at PDFcamp
All printers work, and can print to a normal physical printer via foxpro.
I asked to check if the pdfprinter was enabled/disabled.. haven't heard anything back, hopefully it was that.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The author is NOT using Windows 7, using Vista.
FoxPro is printing fine in Vista to any physical printer. It is having problem with the Very PDFcamp printer, which is not a physical printer.
Printing to Very PDFcamp from any application is causing printer not ready (from what I'm gathering)
PDFcamp so far seems to be the main issue.
Already know about foxpro/dos printing, it doesn't apply here as it's printing to windows printer fine. Just not the pdf printer.
FoxPro is printing fine in Vista to any physical printer. It is having problem with the Very PDFcamp printer, which is not a physical printer.
Printing to Very PDFcamp from any application is causing printer not ready (from what I'm gathering)
PDFcamp so far seems to be the main issue.
Already know about foxpro/dos printing, it doesn't apply here as it's printing to windows printer fine. Just not the pdf printer.
ASKER
1. >> I asked to check if the pdfprinter was enabled/disabled.. << I did not see an enable/disabled option when right clicking on the printer in printer window. However. it shows as ready. Also...
2. >>Printing to Very PDFcamp from any application is causing printer not ready (from what I'm gathering<< That is NOT correct. Every other app can use Very PDFcamp printer just fine. However,
3. Very PDF company had me try their "simple" printer driver that does not have the options that its Pro version has (that I need) and even Foxpro can create a PDF with that version as it also can with PDF995, Adobe, PrimoPDF and CutePDF. So.. it's the combination of their Pro version AND Foxpro that is causing the problem. They've promised to look into it. In the meantime,if there's no solution, I'll have to use an XP machine for this application or create three individual PDF's using the simple printer driver and then combine them in a separate step. Microsoft stopped supporting this non-Visual Foxpro product many years ago. Can't upgrade to visual since it's an OOP product entirely different than FW 2.6 and would break my code.
I had also tried setting Foxpro to run in XP compatibility mode. Didn't help.
If no one has any further questions/suggestions, I suppose I should close this??
2. >>Printing to Very PDFcamp from any application is causing printer not ready (from what I'm gathering<< That is NOT correct. Every other app can use Very PDFcamp printer just fine. However,
3. Very PDF company had me try their "simple" printer driver that does not have the options that its Pro version has (that I need) and even Foxpro can create a PDF with that version as it also can with PDF995, Adobe, PrimoPDF and CutePDF. So.. it's the combination of their Pro version AND Foxpro that is causing the problem. They've promised to look into it. In the meantime,if there's no solution, I'll have to use an XP machine for this application or create three individual PDF's using the simple printer driver and then combine them in a separate step. Microsoft stopped supporting this non-Visual Foxpro product many years ago. Can't upgrade to visual since it's an OOP product entirely different than FW 2.6 and would break my code.
I had also tried setting Foxpro to run in XP compatibility mode. Didn't help.
If no one has any further questions/suggestions, I suppose I should close this??
Sorry for the confusion on number 2. Adobe pdf and cutepdf doesn't append like verycamp?
ASKER
Correct. Of all the "printer to pdf" programs (and I hunted) , only VeryPDF Pro had the append/insert/overwrite option.
I know you are not using W7 but you could try them (only NaturaTek does not know that I know :-). Their compatibility with XP programs is much better than Vista and it is better option than to go back to XP.
It is not necessary to use OOP in Visual FoxPro because it is backward compatible to old FoxPro for Windows versions. You can simply compile and execute all your source code (means programs, reports, and generated screens). You cannot use screen builder as you know it from FoxPro in VFP but you can still generate screens in FoxPro 2.6 and compile them under VFP. Some incompatibilities may occur, of course. If such situation happens you may ask in FoxPro Database zone for solution.
It should even be possible to use VFP just for reports which are saved to PDF.
BTW, did you find/try Win2PDF? http://www.win2pdf.com/products/win2pdf.htm
It is not necessary to use OOP in Visual FoxPro because it is backward compatible to old FoxPro for Windows versions. You can simply compile and execute all your source code (means programs, reports, and generated screens). You cannot use screen builder as you know it from FoxPro in VFP but you can still generate screens in FoxPro 2.6 and compile them under VFP. Some incompatibilities may occur, of course. If such situation happens you may ask in FoxPro Database zone for solution.
It should even be possible to use VFP just for reports which are saved to PDF.
BTW, did you find/try Win2PDF? http://www.win2pdf.com/products/win2pdf.htm
ASKER
Confused: >>I know you are not using W7 but you could try them << try them? What's "them".
BTW, I tried Win2PDF and it generates the same Printer not ready error. Shame since it has the "prepend/append/overwrite"
BTW, I tried Win2PDF and it generates the same Printer not ready error. Shame since it has the "prepend/append/overwrite"
Sorry, that's my English... W7 means Windows 7, therefore "them" means "Windows 7" :-) May be I should write "it" instead of "them"...
But it does not matter. Microsoft is proposing much better compatibility with XP programs in Windows 7 than in Vista. So, my recommendation was to install Windows 7 and try it.
The Visual FoxPro still could be a solution.
But it does not matter. Microsoft is proposing much better compatibility with XP programs in Windows 7 than in Vista. So, my recommendation was to install Windows 7 and try it.
The Visual FoxPro still could be a solution.
You don't make any sense elba, do you know something that I don't? Because there is NO Windows 7 compatiblity in Vista, the author is using Windows Vista.
Are you trying to recommend the author installs Windows 7? If so, it's not officially released yet, only a candidate exists and it's up to the author if he wants to shell out the cash for a new OS.
Are you trying to recommend the author installs Windows 7? If so, it's not officially released yet, only a candidate exists and it's up to the author if he wants to shell out the cash for a new OS.
i would still recommend upgrading to Visual FoxPro 9.0
Yes, I am recommending to install Windows 7. If it will work then we have the solution... The fact it is RC instead of final version is not relevant for now. It is just 1 hour delay to install Windows 7. If it will be unsuccessful then XP will help.
I know author is using Vista. And if there is no "Windows 7 compatibility" in Vista it could mean just advantages and possibility of success.
I know author is using Vista. And if there is no "Windows 7 compatibility" in Vista it could mean just advantages and possibility of success.
Awful recommendation when it's not proven. Why don't you install foxpro 2.6 and very pdfcamp on your Windows 7 computer and post your experience, then maybe you can offer that recommendation if it works.
ASKER
now now boys, don't fight. i have a separate machine with xp. i was never going to go back to xp. would just prefer to do all the work on the vista machine
I would say we are sharing ideas not only proven solutions. Hope it was visible from my answers. If somebody would know the answer then this question is closed already...
This is not fighting, just a discussion :-)
This is not fighting, just a discussion :-)
ASKER
Just jokin' wit' ya' pcelba!
But no, I don't consider the questions closed. I just haven't heard a solution. The only solution that I would consider is a way to make my current config (Vista, Foxpro 2.6, and VeryPDF) work. OR a substitute for VeryPDF that WOULD work that has the "prepend/append/overwrite"
But no, I don't consider the questions closed. I just haven't heard a solution. The only solution that I would consider is a way to make my current config (Vista, Foxpro 2.6, and VeryPDF) work. OR a substitute for VeryPDF that WOULD work that has the "prepend/append/overwrite"
Yeah, nothing like telling a user 'hey pdf printer don't work in vista? go and install windows 7'..when windows 7 isnt officially released yet and its not proven it will work in 7.
Hey that cooking oil not making your fries crispy? Here, take my Mobil 1 5w30 motor oil..havent tested it for cooking but I think the viscosity is better.
Hey that cooking oil not making your fries crispy? Here, take my Mobil 1 5w30 motor oil..havent tested it for cooking but I think the viscosity is better.
Windows 7 is official RC. And even at this stage it is much better than Vista RTM. It was the main reason of my suggestion. Do you think Windows 7 will change significantly before going live?
It seems there are just two solutions of this problem acceptable by Fritters:
1) Update FoxPro to ignore "Printer not found" message
2) Update VeryPDF to behave better in conjunction with FoxPro 2.6 under Vista
Everything else means some software or OS change which is not considered as a solution.
The VeryPDF update seems to be the only option because FoxPro cannot be updated by standard way.
BTW, do you know the used cooking oil is possible to use as a fuel for old diessel cars?
And what about executing this report in Visual FoxPro?
It seems there are just two solutions of this problem acceptable by Fritters:
1) Update FoxPro to ignore "Printer not found" message
2) Update VeryPDF to behave better in conjunction with FoxPro 2.6 under Vista
Everything else means some software or OS change which is not considered as a solution.
The VeryPDF update seems to be the only option because FoxPro cannot be updated by standard way.
BTW, do you know the used cooking oil is possible to use as a fuel for old diessel cars?
And what about executing this report in Visual FoxPro?
Yes it's RC, and that's all that it is RELEASE CANDIDATE.
Wisegeek: A release candidate, like a beta version, is currently working, but has several identified glitches that must be addressed before the program can be test marketed to a small sector of consumers. By contrast, the beta version has generally already been refined to fix those identified bugs, and is ready for limited use and evaluation by a handful of consumers. This in essence makes the release candidate the precursor to the beta version.
This is in NO way a final official released product. The RC that is available for download will end around July 2009 and it will shutdown bihourly as of March 1 2010
Microsoft says "Windows will notify you that the expiration process is beginning and two weeks later your PC will begin shutting down every two hours", so you should have fair warning.
By then, the person has buy their own copy of windows 7 (no exact on prices now, though there are speculations on what it could cost), and of course, uninstall and install the official release.
While 7 is a better upgrade to vista (don't they always say that anyway? 98 better than 95, vista better than xp..etc) The point being, it's not plausible to recommend to a client (user in this case) a operating system thats not in it's official version yet and it will expire, having to uninstall..BUY it..and install the retail copy. All that when it's not proven it will help the user with the pdfprinter problem. Shouldnt suggest such a vast road to a new os thats not in its official version yet and not proven to work out the users problem. Do more harm than any good, including the user obtaining win7 drivers for his equipment.
Wisegeek: A release candidate, like a beta version, is currently working, but has several identified glitches that must be addressed before the program can be test marketed to a small sector of consumers. By contrast, the beta version has generally already been refined to fix those identified bugs, and is ready for limited use and evaluation by a handful of consumers. This in essence makes the release candidate the precursor to the beta version.
This is in NO way a final official released product. The RC that is available for download will end around July 2009 and it will shutdown bihourly as of March 1 2010
Microsoft says "Windows will notify you that the expiration process is beginning and two weeks later your PC will begin shutting down every two hours", so you should have fair warning.
By then, the person has buy their own copy of windows 7 (no exact on prices now, though there are speculations on what it could cost), and of course, uninstall and install the official release.
While 7 is a better upgrade to vista (don't they always say that anyway? 98 better than 95, vista better than xp..etc) The point being, it's not plausible to recommend to a client (user in this case) a operating system thats not in it's official version yet and it will expire, having to uninstall..BUY it..and install the retail copy. All that when it's not proven it will help the user with the pdfprinter problem. Shouldnt suggest such a vast road to a new os thats not in its official version yet and not proven to work out the users problem. Do more harm than any good, including the user obtaining win7 drivers for his equipment.
ASKER
How do I close this question? Or should I leave it in case someone stumbles on it and has an "answer"?
hang on..i'm gonna attempt to do something. going to look for foxpro 2.6 , gonna load it in my vista station with pdf printer. I'll get back to you.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
No real solution. Good effort.
fyi, tried the above combo in Windows 7, same exact results. No dice. Take care.
You did perfect work, NaturaTek! And thanks for testing it in Windows 7.
Everything I can offer is the help with porting the report into Visual FoxPro, so if you are interested, Fritters, let me know.
Everything I can offer is the help with porting the report into Visual FoxPro, so if you are interested, Fritters, let me know.
ASKER
Foxpro is very old. Foxpro for Windows Version 2.6a. But as I said, even under XP Pro, this Foxpro and PDFCamp printer driver worked. Is there some difference with the way that Vista handles printers?