[Bug 47933] New: FoxPro for Windows 2.6a will not print output from scripted dialog.

WineHQ Bugzilla wine-bugs at winehq.org
Mon Oct 14 13:43:59 CDT 2019


https://bugs.winehq.org/show_bug.cgi?id=47933

            Bug ID: 47933
           Summary: FoxPro for Windows 2.6a will not print output from
                    scripted dialog.
           Product: Wine
           Version: 4.0.1
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: programs
          Assignee: wine-bugs at winehq.org
          Reporter: JSladek at juno.com
      Distribution: ---

Created attachment 65436
  --> https://bugs.winehq.org/attachment.cgi?id=65436
General format for program sections

Access to and use of my databases is all under a program written using the
FoxPro language.  After opening the desired database and index, I use the
command "REPORT FORM <report format filename> TO PRINTER" to send the report to
the printer.  The "TO PRINTER" clause can be substituted by "TO FILE
<filename>" .... however ..... in BOTH cases, while running it in WINE, the
output fails with a "printer not ready" error.  Additionally, if I replace the
"TO clauses" with "PROMPT", a printer selection (or to file) dialog comes up,
but I still get the same "printer not ready" error regardless which selection I
make.

Using the "PREVIEW" option to the REPORT FORM command instead of "TO PRINTER" I
can view the entire formatted report, but there is no way that the preview can
be redirected to any other type of output.

It appears to me that the way the command set is structured, the only way to
get a report output is through the "report form / printer" interface.  It also
appears that the "to file" direction is through that same interface.

There were a couple of submnissions concerning this problem in the 2008 time
frame.  The only solution offered was to adjust tyhe TIME function for faster
processors in the FoxPro config file.  I tried this, but it has no effect on
the problem.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.



More information about the wine-bugs mailing list