Strange Results using NIReport Functions

[ACL]

I have been having problems using the NIReport Functions.

One problem is that the margins won't set separately. The top and bottom margins are always mirrored and the left and right margins are always mirrored.

Another problem is that I can't create a NIReport Table thats wider than 9" in Landscape and 6.5" in Portrait mode.
Asking for anything more results in garbage being printed.

I have tried this with multiple printers on different computers and I always get the same results.

I have attached a small test program that demonstrates the problem.

Does anyone else have a problem that I describe?

[Jeremy_L]

Hi,

Unfortunately I cannot reproduce the issue you are running into here on my machine. I have tried both setting unequal margins in landscape and portrait, as well as specifying a table longer than 9" in landscape and 6.5" in portrait modes. I've consistently made a printout that shows my settings. Here I am using Windows XP SP 2 and a Ricoh Laser Printer. I'm wondering if it has something to do with your printers. Are you testing this on printers of different brands or models? Also, what version of CVI are you running? Thanks!

Jeremy L.
National Instruments

[ACL]

I'm using LW/CVI 7.1 on W2k Pro.
I have the same problem using a HP1220, a HP6100 and the HP4050 printers.

I've attached some scans of the output in Landscape (9.5" requested) and Portrait modes from the HP1220 (7.0" requested).
The output on the other printers is similar if not identical.

Is there possibly another setting from either LW/CVI (eg.. SetPrinterAttribute()) or on the printer dialogs that you can think to set?

I've read the Knowledgebase stuff about non-compliant printer drivers at this link which doesn't give me a warm feeling about the situation...
Link to Printer Driver Problem
Askin
g or waiting for HP to provide a solution could be a problem. As it stands with the implementation of the Table Reporting feature (NIReport_ConvertCVITable()) in NIReports, you can't control the column widths without using TableStart() and TableEnd(), but then you have to lose paper real estate if you limited in the printer (drivers) you have.

As always thanks for helping, its a real service to the outside world.

[Jeremy_L]

Yeah, I've seen some problems with these HP drivers and LabVIEW, which incidentally uses GDI as well. Is there a way for you to test this on a non-HP printer to see if it's really related to HP's drivers? I don't have access to an HP Printer here, and so I unfortunately cannot test it. A better idea may be to take a small example of your code that reproduces the issue and see if it happens on any of my printers. This way at least we can see the difference on your code between using HP Printers and Non-HP Printers. Sorry for the inconvenience. If we notice something strange, I'll be sure to document it and send to R&D for further investigation.

Jeremy L.
National Instruments