VFP9 Reports

Hot Topic

Starting EXE fails, asks for missing FXP
Help with query in VFP 9.0
Converted VFP 3.0 Project
Query help
HOW I CAN DO "WIZARD UPSIZING" FROM THE SOURCE CODE??
Need help on a small open table code
Programatically Placing Controls on a Form
Export data to text- How I can bypass the default text delimitter?
Excel validation
stop “invalid input”

Visual FoxPro

DO FORM does not work in exec (for me)
Help?
FoxPro character fields in .Net showing as blank strings.
Menu Pad Name Errors VFP80 - VFP90
VFP9 Multiple Detail Bands and Page Overflow
Use ADIR to get specific files from a folder
editbox programmatic change
Keypress Event question and ALT + L
use the reccount
Cannot updat the cursor FOXRESOURCE, since it is read only.

VFP9 Reports

Has anyone experienced this issue

  1. Create a report
  2. In design mode, Right Click on the report and select "Properties"
  3. On the "Page Layout" tab select "Page Setup"
  4. Choose "Landscape" as the Orientation.
  5. Click "OK" and the check the "Save printer environment" checkbox on the Page "Layout" tab.
  6. Click "OK" and save the changes to the report.
  7. Issue the command "Report Form MyReport.frx NOEJECT NOCONSOLE PREVIEW"
  8. The Report displays correctly in landscape mode.
  9. Issue the command "Report Form MyReport.frx NOEJECT NOCONSOLE PROMPT PREVIEW"
  10. The Report displays correctly in landscape mode, but when choosing to print, the report prints in Portrait mode
  11. Issue the command "Report Form MyReport.frx NOEJECT NOCONSOLE PROMPT to Printer"
  12. Select the printer and print the report.  It prints in Portrait mode.
  13. Issue the command "Report Form MyReport.frx NOEJECT NOCONSOLE to Printer"
  14. The report prints correctly in Landscape mode.
 
  1. The issue seems to be with using the "PROMPT" keyword.  It seems that when the Print Dialog box is displayed, the printer's settings revert to it's default settings.
  2. This is not the case in any version previous to VFP9
  3. This behavior occurs even when setting REPORTBEHAVIOR to 80
  4. Setting Resource to off has no effect


Answer this question

VFP9 Reports

  • ralfkret

    Hi Bill

    Seems to be OK when I try this. Do you have SP1 for VFP 9.0 installed If not, maybe you should try it and see if that fixes it for you.

  • Kuido Klm

    HI Bill

    Actually it is unlikely that you will ever hear back from them. They do not normally reply to bug reports. I would send another if I were you, and include as much info has you have - the more they have, the more likely it is that they can figure out what is going on.

  • JDT

    Hi Bill

    Sorry, but I don't have the resources to test this.

    You could always report it as a VFP 9.0 bug (details of how to do this are on the "support" page at the VFP Home page on Microsoft's website).

    This does sound like some sort of conflict issue - though I cannot imagine what could produce this result...wierd!

  • Shafa

    I actually did report this to Microsoft, but I did not include my findings about the printer connected to WTS.  I have not heard from them, I'm wondering if I can edit the one I sent, or should I send another one   Anyway, thanks again for your responses.

  • dcallan

    Andy, Thanks for the response.

    I installed SP1, and am still getting the same results.  But, I also have some additional info. 

    There are a specific set of circumstanses that produce this result.  It seems I only get this behavior when I have my default printer set to a shared printer that is set up on a server that is running WTS.  Keep in mind that I am not accessing this printer through WTS, but have it set up on my machine.

    If I have my default printer set to a printer connected to my local machine, I do not experience this behavior.

    If I have my default printer set to a printer connected to another computer (Not running WTS) on the network, I do not experience this behavior.

    Even if I access a different printer through the print dialog box, the portrait/landscape setting remains the same. 

    I checked this using VFP8, and I do not experience this issue.


    If you have the resources, see if you obtain the same results.  Thanks again.
  • VFP9 Reports
Answer this question