Printing to HP printer causes Blue Screen
-
- Posts: 62
- Joined: Mon Dec 11, 2006 1:43 pm
- Location: U.S.A.
Printing to HP printer causes Blue Screen
When we print from the designer to an HP printer we get a blue screen. This has happened with a HP 8150 and a HP 3120 printer. We also had a customer report a blue screen with his HP printer.
Has anyone else experienced this?
Any ideas?
Thanks,
Sandy
Has anyone else experienced this?
Any ideas?
Thanks,
Sandy
Printing to HP printer causes Blue Screen
Here is a small .Net application which prints one line using .Net Framework only. Please try to print with this application and let us know about results.
Thank you.
Thank you.
- Attachments
-
- 46.NetPrint.zip
- (31.72 KiB) Downloaded 529 times
-
- Posts: 62
- Joined: Mon Dec 11, 2006 1:43 pm
- Location: U.S.A.
Printing to HP printer causes Blue Screen
This application works fine.
I am sending you a report that produces the blue screen.
I am sending you a report that produces the blue screen.
Printing to HP printer causes Blue Screen
If possible please send a data for the report or an mdc(mdz) file as well. We were unable to reproduce the issue on HP printer.
Also there are few components inside your report. If possible, please try to remove one, then another component, until the report would cause a blue screen and let us know which component is responsible of such a behavior.
P.S. Sometimes updating a printer driver helps in resolving similar situations.
Thank you.
Also there are few components inside your report. If possible, please try to remove one, then another component, until the report would cause a blue screen and let us know which component is responsible of such a behavior.
P.S. Sometimes updating a printer driver helps in resolving similar situations.
Thank you.
-
- Posts: 62
- Joined: Mon Dec 11, 2006 1:43 pm
- Location: U.S.A.
Printing to HP printer causes Blue Screen
I have narrowed the problem down to occurring when there is text on the title bar or column headers present. We have several customers that are reporting the same problem. Here is a list of the HP printers we know of that have a problem and the ones that work fine. Is there anyone else on the forum that is experiencing this issue?
Blue Screen
---------------
HP Laserjet 2300
HP Laserjet 3005
HP Laserjet 3120
HP Laserjet 8150
Print without error
---------------------
HP Laserjet 2100 TN
HP Office Jet 7400
Thanks,
Sandy
Blue Screen
---------------
HP Laserjet 2300
HP Laserjet 3005
HP Laserjet 3120
HP Laserjet 8150
Print without error
---------------------
HP Laserjet 2100 TN
HP Office Jet 7400
Thanks,
Sandy
Printing to HP printer causes Blue Screen
We have a Laserjet 2300D. Could you post a report that does not, so I could test it?
Thanks a lot
Marco
Thanks a lot
Marco
Printing to HP printer causes Blue Screen
Thank you for your help, Marco.
Here you are.
Thank you.
Here you are.
Thank you.
- Attachments
-
- 51.ReportTitleBandAndTitle.mrt
- (43.82 KiB) Downloaded 630 times
-
- 50.NoTextOnTitleColHdrOrFooter.mrt
- (43.96 KiB) Downloaded 534 times
Printing to HP printer causes Blue Screen
When I load both reports in the designer, click on preview and then on print both print without a problem.
Marco
Marco
Printing to HP printer causes Blue Screen
Please provide me with the link to drivers you are using or just driver version installed.
I am suspecting that this will be the answer.
Thank you very much, Marco!
Thank you.
I am suspecting that this will be the answer.
Thank you very much, Marco!
Thank you.
-
- Posts: 62
- Joined: Mon Dec 11, 2006 1:43 pm
- Location: U.S.A.
Printing to HP printer causes Blue Screen
I think I have a clue to the problem. I do not believe it is the printer driver because I am now able to create new reports that print fine on the HP printers. However, existing reports still blue screen.
I pass my data to the report via a DataSet. I set up DataRelations so that the report tree will know which tables are joined. I used to set relationships going both ways. For example, if I had TableA and TableB I would create 2 DataRelations - one from TableA to TableB, one from TableB to TableA. I also use intermediate join tables sometimes. For example, TableA connects to JoinTable which connects to TableB. In this case I create 4 DataRelations - Table A to JoinTable, JoinTable to TableB, TableB to JoinTable, JoinTable to TableA.
While looking at this bug, I expanded the report tree and noticed that there were lots of duplicated tables -- TableA and TableA2, JoinTable and JoinTable2 and JoinTable3. So, it appears the Data Tree building code is different now. I decided to try only sending the relationships in one direction (just TableA to TableB). That works and the tree doesn't have extra tables listed. And, any new report I create prints just fine.
I tried adding some code to clear out the extra tables in the Tree View. I added:
report.Dictionary.Relations.Clear();
before I call Synchronize(). That makes the tree correct. Is there anything else that would be hanging around that I could clear programmatically?
Thanks!
I pass my data to the report via a DataSet. I set up DataRelations so that the report tree will know which tables are joined. I used to set relationships going both ways. For example, if I had TableA and TableB I would create 2 DataRelations - one from TableA to TableB, one from TableB to TableA. I also use intermediate join tables sometimes. For example, TableA connects to JoinTable which connects to TableB. In this case I create 4 DataRelations - Table A to JoinTable, JoinTable to TableB, TableB to JoinTable, JoinTable to TableA.
While looking at this bug, I expanded the report tree and noticed that there were lots of duplicated tables -- TableA and TableA2, JoinTable and JoinTable2 and JoinTable3. So, it appears the Data Tree building code is different now. I decided to try only sending the relationships in one direction (just TableA to TableB). That works and the tree doesn't have extra tables listed. And, any new report I create prints just fine.
I tried adding some code to clear out the extra tables in the Tree View. I added:
report.Dictionary.Relations.Clear();
before I call Synchronize(). That makes the tree correct. Is there anything else that would be hanging around that I could clear programmatically?
Thanks!