Printing Issue when migrating from Paradox 8 to 11

Greetings,

We used a pushbutton method on a form to print a report in Paradox 8 and Windows 7.  Upon upgrading to Paradox 11 the report began failing with a "#Bitmap7 is too big to fit in report." error.

• #Bitmap7 is a full-page 8.5x11 image
• The error is printer independent, and fails even with a PDF printer
• The report still works fine on any printer if you open the report and print directly from that
• Shrinking the image and placing it in the middle of the page solved the problem too
• Recucing the file size dramatically didn't help if left at 8.5x11

It must be that Paradox 11 is trapping an error based on image size that Paradox 8 didn't.  Is there any way to prevent it from doing this, or to tell the method to ignore the error and print anyhow?

Might there be anything else obvious that I am missing?

Thanks!

the question is whether you can trap for that error, in that context, to at least find out if it'll let you "pass go and collect $200".. I honestly don't know

if you can just shrink and center the image, and move on, that would seem to be the easiest path, if you can just shrink it a little bit

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

Hi Steven,

Thanks for the prompt reply. I was afraid that was the answer, but as you say at least I can move on. It will be very tedious to shrink the images, but not as tedious as finding the error in the haystack, particularly because I don't know what I am doing.

Thanks again for your help! I am so glad to see people still using Paradox.

it could be your margins, your printer drivers, win10 itself, an error that you can't trap and/or bypass, etc..

even if it's 50 reports, it's a simple change you already know you CAN do, and it works.. I'd do that :-)

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

Thanks again for your insight. 

I went about changing the templates as you suggested.  It did indeed seem a clear path to victory.  Unfortunately as I expanded the image past the 1"x1" size I shrank it to for troubleshooting purposes it quickly began to fail again.  I need to leave 1.25" top and bottom margin or it won't work.  This crops off critical data, so I will have to keep digging a bit.

One clue might be that 11-2.5=8.5   Maybe I am shooting a portrait report at a landscape page?  I'm not sure where or why Paradox would suddenly think my format is landscape, but it is something to look for at least.

I'll report back if I solve the problem in case it helps anyone with a similar issue.

It also started printing a blank page after the correct one just to spite me.  Probably the same issue.

Steve

the "blank page" comment triggered a memory of a similar issue.. here's how we dealt with it.. the essential snippets.. this made the blank page go away, and that report also had a huge insert, but we weren't having the pic issue you were

var

repinfo reportprintinfo

endvar

repinfo.name = "SUBASSEMBLYREPORT.RSL"
repInfo.PanelOptions = PrintClipToWidth ; <[;_--]-

if not REP.print(repinfo) then

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

Thanks!  I'll try that.  The image issue also seems to be a result of some change in repInfo.  In Paradox 8 we explicitly declared a prnopinfo.PaperLength but had to rem out because of another migration error.  That might have been more necessary than I thought...

I don't have p8 loaded right now.. not finding anything specific in the bug list.. report issues can be tricky, and annoying

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

Progress!

The offending code was:

repinfo.orient = PrintPortrait

Go figure?  It is a portrait-format report!

This thread on another site suggests that the ReportPrintInfo syntax changed between P9 and P10, and that P10 and beyond uses a DynArray syntax.  I haven‘t looked into that yet.

Also, once it was printing, your repInfo.PanelOptions = PrintClipToWidth hint prevented the printing of the blank page.  Thanks for that!

I‘ll post if I learn anyting more.

Steve

that link didn't work, but yes, there are a handful of tweaks in p10 that aren't in the help files.. p10 was a work inprogress when the end came

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

 Sorry about the link.  It may require login.  Anyhow, the key bit was:

What version of Paradox are you using? If 10 or greater, ISTR I had some problems doing this with 10 quite a while back, and with Bertil's help worked out to set the paper size (A4) using the old syntax, and then set clip-to-width, orientation etc using the new, dynarray syntax.

This seems to match with my finding that setting the orientation was my problem in the old syntax.

Printing issue with migrating the document are the error of driver software of printer that will not give it a right command to printer for print a document.

Available here https://garagedoorinsulationpros.com/ Garage Door Insulation Installation Company in The Villages