I have applied a solution, by using foxypreviewer. I avoided using Foxy early on, thinking it was too many keystrokes/mouse clicks, but really, I should have used it earlier on.
It still beats me why "set printer to name (name) " gave me the errors On Wed, Jul 23, 2014 at 10:53 AM, Sytze de Boer <sytze.k...@gmail.com> wrote: > I am confident all the runtime settings are latest version > > I have a theory that I need to test, which is to install the same printer > on the pc as a local printer > Then change the port settings to the shared printer at the far end of the > building. > > > > > On Wed, Jul 23, 2014 at 10:49 AM, Fred Taylor <fbtay...@gmail.com> wrote: > >> OK, but I've only ever seen that issue if there report has the printer >> environment included and the particular printer is not available to the >> workstation that's trying to run the report. I've never seen it if the >> environment is empty. You do have the HotFix that corrects the issue with >> VFP9 resetting the include printer environment checkbox if you modify the >> report. In other words, you do have the latest version of VFP and the >> runtimes match that version, correct? >> >> Fred >> >> >> On Tue, Jul 22, 2014 at 3:37 PM, Sytze de Boer <sytze.k...@gmail.com> >> wrote: >> >> > Fred, thank you, but already covered >> > Please refer my post that said >> > No problem if I embed the network printer in with the Report, and >> set >> > printer environment on >> > (This is not a practical solution) >> > >> > >> > >> > On Wed, Jul 23, 2014 at 10:36 AM, Fred Taylor <fbtay...@gmail.com> >> wrote: >> > >> > > Make sure you do not have any printer embedded in the report. VFP9, >> > > uncheck the Save Printer Environment under the File/Page Setup... >> > dialog. >> > > >> > > >> > > Fred >> > > >> > > >> > > On Tue, Jul 22, 2014 at 3:31 PM, Sytze de Boer <sytze.k...@gmail.com> >> > > wrote: >> > > >> > > > Tracey, as always, I appeciate your advice >> > > > >> > > > So, I just tried the Notepad trick. It prints fine ! >> > > > >> > > > >> > > > >> > > > On Wed, Jul 23, 2014 at 10:29 AM, Tracy Pearson < >> tr...@powerchurch.com >> > > >> > > > wrote: >> > > > >> > > > > Sytze de Boer wrote on 2014-07-22: >> > > > > > >> > > > > > Error accessing printer spooler >> > > > > > >> > > > > > When I do this at my place, no problem if i print to a local >> > printer >> > > > > > No problem if I embed the network printer in with the Report, >> and >> > > set >> > > > > > printer environment on >> > > > > > (This is not a practical solution) >> > > > > >> > > > > Sytze, >> > > > > >> > > > > When we hear that, we ask the user to print from Notepad. They >> > usually >> > > > > cannot. A system restart is the simplest solution. >> > > > > >> > > > > The other reason is the default Windows Printer is actually not >> set, >> > or >> > > > > offline. Changing the default printer fixes it in this case. >> > > > > >> > > > > Tracy Pearson >> > > > > PowerChurch Software >> > > > > >> > > > > [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/cag1nny-6ial_ej33cnvuxpdpjwxhmzfezuzrw0ticj1gh8d...@mail.gmail.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.
