memo fields not printing
Delphi 7. ReportBuilder Pro 7.03
We are using a TppDBMemo in a detail band to show the description of an
item. We have these reports used by lots of clients and it all seems to work
well. But there is always one where it doesn't! For this particular client
the item description is simply blank. Its blank in screen preview and the
printed report (so at least its consistent from that viewpoint). However,
even for this client, they have it working on their test system but just not
the live system. My initial reaction was that it was a printer driver. They
are using an OKI printer. They have tried the OKI printer driver, a HP
driver and a Generic/Text driver. All drivers work on the test system but do
not work on the live system. They are using Terminal Services and have tried
to check that angle as well. And this is where it starts to get interesting.
If I understand them correctly (I'm trying to get it verified by them) they
were able to make the test system stop working. There are two settings
available when logged on under RDP - "Connect client print at logon" and
"Windows printer mapping". When these two settings were disabled, they got
the problem with no memos printing out.
The client is getting pretty irate wondering why we can't produce a report
that can show a description so any help would be appreciated.
Regards
Jeff
We are using a TppDBMemo in a detail band to show the description of an
item. We have these reports used by lots of clients and it all seems to work
well. But there is always one where it doesn't! For this particular client
the item description is simply blank. Its blank in screen preview and the
printed report (so at least its consistent from that viewpoint). However,
even for this client, they have it working on their test system but just not
the live system. My initial reaction was that it was a printer driver. They
are using an OKI printer. They have tried the OKI printer driver, a HP
driver and a Generic/Text driver. All drivers work on the test system but do
not work on the live system. They are using Terminal Services and have tried
to check that angle as well. And this is where it starts to get interesting.
If I understand them correctly (I'm trying to get it verified by them) they
were able to make the test system stop working. There are two settings
available when logged on under RDP - "Connect client print at logon" and
"Windows printer mapping". When these two settings were disabled, they got
the problem with no memos printing out.
The client is getting pretty irate wondering why we can't produce a report
that can show a description so any help would be appreciated.
Regards
Jeff
This discussion has been closed.
Comments
Are your clients able to see any other objects on their reports, besides the
memos? Are any other data fields being displayed correctly? If so, you
need to take a look at the data angle. ReportBuilder uses the same logic to
access and display normal DBText and DBMemo components. If one is showing
up and the other isn't, it must be a data access issue.
--
Regards,
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
doesn't appear to be a problem as the report can work on some systems. I
don't understand what you think is the data that could cause a problem. I'm
leaning towards terminal services myself. I've seen weird things before with
it. As I explained in my original topic, it works on a test system but if
they change a couple of terminal services settings it no longer works. That
doesn't seem to be data.
This is not a known issue with ReportBuilder and Terminal Services. We have
many customers using Terminal Services successfully and usually the only
problem we encounter is that the client does not have proper access to the
printer driver. This probably isn't relevant in your case because you are
getting some things to print. Here are a couple things you might try to
isolate the problem...
1. Have your client print to a different printer and see if the results are
the same (i.e. different printer, different printer driver).
2. As I mentioned before ReportBuilder uses the same logic (even the same
code) to render both text and memos to the screen and printer. If you have
access to your clients environment, try placing a stop inside the
DrawStandardText routine located in the TppScreenDevice class in the
ppViewer.pas file. First check the value of the aDrawText.WrappedText
property to see if the text is even present (data issue). Next step through
the routine to perhaps find out where RB is loosing the text.
--
Regards,
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com