Report will display but not print

Meeting place for R&R customers and clients to share tips and ideas. Post your questions, messages or problems here.
Post Reply
jstiegler
Posts: 23
Joined: Tue Oct 10, 2017 12:44 pm

Report will display but not print

Post by jstiegler » Mon May 19, 2003 3:31 pm

We use R&R 8.1 with VB6 ... some users with XP Windows, home or professional, report that some reports must be displayed first before printing. Not all XP computers experience this problem. Also, sometimes a report will not exprience this problem, but will develop it later. This does not seem to be a problem with earlier versions of Windows.____Please help.

Thomas_Freitas_(Guest)
Posts: 123
Joined: Tue Oct 10, 2017 12:44 pm

=> Report will display but not print

Post by Thomas_Freitas_(Guest) » Mon May 19, 2003 4:52 pm

Below is a note that Kathleen had sent out earlier. You should also be able to enter "DEFAULT" in their RRWRUNIN.DBF file, if you are using one.________Kathleen Wrote: ____When a report is opened in Version 9 or below, R&R will attempt to find/use the printer that is saved with the report. If the printer cannot be found, then it will default to the user^s default printer. In Version 10 , there is a setting that will allow you to force a saved report to use a particular printer.____One thing that your users can do is to use RRWRUN.EXE in place of RRW.EXE and to set up a runtime control file.____So you would create a text file (called myreport.txt for this example)__with the lines:__ RI_REPORT=REPORT.RRW__ RI_WPTR=DEFAULT____ then you would use the command line:__ RRWRUN.EXE /Tmyreport.txt____and the report.rrw would be run using the user^s default printer.____

jstiegler
Posts: 23
Joined: Tue Oct 10, 2017 12:44 pm

==> Report will display but not print

Post by jstiegler » Mon May 19, 2003 7:03 pm

[updated:LAST EDITED ON May-19-03 AT 07:03 PM (EST)]Will upgrading to v10.xxxx solve my problem?

kfleming
Posts: 5795
Joined: Tue Oct 10, 2017 12:44 pm

===> Report will display but not print

Post by kfleming » Mon May 19, 2003 8:36 pm

Depends what the problem really is.__Are you using runtime? If so what values are you setting to control report output?__Are the users getting an error message?____Kathleen__R&R Support

jstiegler
Posts: 23
Joined: Tue Oct 10, 2017 12:44 pm

====> Report will display but not print

Post by jstiegler » Mon May 19, 2003 9:49 pm

We are using the VB Control (RRW32.ocx and supporting files) to run report from our Visual Basic 6 application.____This problem only surfaced in the last few months. It only occurs on a few XP computers ... but not all XP computers. This does not happen on Win98, Me computers.____When users try to print, they receive a run-time error concerning the rrwrun.exe .. then our app crashes. Users have found that they can print the report by displaying it first and then printing it from the display ... its an extra step for users.____This does not happen with all of the app^s reports ... some and not others ... there seems not to be a clear pattern. Customer(1) might have a problem with report(A) but customer(2) might NOT have a problem with that report but will have a problem with report(D), for example.____Very strange.

kfleming
Posts: 5795
Joined: Tue Oct 10, 2017 12:44 pm

=====> Report will display but not print

Post by kfleming » Tue May 20, 2003 6:09 am

Do you allow the user to select the printer they wish to use?__If so, have them try using the Properties button prior to printing and see if that avoids the crash.____Kathleen__R&R Support

Thomas_Freitas_(Guest)
Posts: 123
Joined: Tue Oct 10, 2017 12:44 pm

======> Report will display but not print

Post by Thomas_Freitas_(Guest) » Tue May 20, 2003 1:34 pm

I use Visual dBase 5.7 for programing and call up rrwrun.exe from the program. I found out that for some reason Visual dBase does not like the pdf controls in R&R and when I run a report, it crashes. When I deleted the file CDINTF.DLL, the reports ran just fine. I might add here, that Visual dBase 7.x does not have the same problem.____You might try renaming the DLL on a clients computer that is having the problem, just to see if that is the case with you also.____Tom Freitas

Post Reply