Removing printer info on frx

[phita]

Hi,
I am having a problem with reports. When they run on some computers, they show *** on numeric fields while on others they show the figures correctly. How do I make the report printer independent so that they show correctly on all computers, regardless of the default printer on that computer?

Thanks.

 

[Mike Gagnon]

PHITA

Faq184-581 shows you how to remove the printer information from your report. But I'm not sure that will solve your problem. The idea is to test your report on all possible printer configurations and stretch the field so it appears proper on all printers. Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.

 

[rgbean]

phita,
I've seen this happen when the report uses a "non-standard" font. Remember that when Windows is asked to use a font it doesn't have installed, it will substitute one it thinks is "similar", and it may have different characteristics. As Mike suggests, make all the fields just as large as possible to minimize these problems.

Note: Sometimes it's also a matter of bad data, and the report is doing the best it can!

Rick

 

[tondi]

On occasions when I have seen the *** you mention,
it has been because the number exceeded the field size.

Could this be your problem?

Tony

 

[Mike Gagnon]

tondi

I hope that after 5 months phita has resolved his issue. ;-)

Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.

 

[craigsboyd]

I'm everyone else on this one...the *** you are seeing is almost certainly a field size problem. It is always (almost) a good idea to remove the printer specifics from FRX before compiling apps/exe for distribution (as Mike pointed out). Rick brings up a good point about fonts, windows and the printer both with non-standard fonts. I have seen this countless times with numeric fields, margins, lining up lines to form boxes (next to impossible). Trick is to not shave your margin of error too close with reports because they are always close but hardly ever right on.

Slighthaze = NULL