I did a search on this but could not find anything. I have some letters (I think the same would be true if they were reports) that were originally designed in v4 under Win98se printer drivers (HP4 vanilla PCL5). Most of the letter contents are in rtf boxes. In an rtf box I have fields such as name, address and in the text of the letter a field or two for things sucj as company name, etc. As origianlly designed it all printed perfectly (under win98se and v4 and v4.5).
Then 2 things happened: I moved the app to v5 and some network workstations (not all) went to Win2k.
This resulted in some text related to fields printing very small and in some cases overprinting of correctly sized text (one line on top of another). Using win98se I cured all this by simply making a small edit in the rtf (anything, even putting in a zero) and then saving the payout under v5.
But this still did not cure all the problems if a user was using w2k with the very same printer (but of course the printer drivers are different in the differernt OSs). I then determined that Using a w2k machine for development I could cure most of the problems by going into the rtf, selecting all text (including the fields) and making a small change to font or the font size and then saving the layout.
This cured all the overprinting and most of the changes to tiny print--but not all. In some cases, usually where a field is involved (such as an address) the print is still very tiny. That is, tiny when printed under w2k but it shows the correct size in the layout and it still prints correctly under win98se to the very same printer!
I would hate to have to rebuild all the layouts in v5 as there are many of them and most of them are not simple. Any ideas as to what is going on and a cure that does not require rebuilding everything from scratch?
Barring any good ideas, I guess I will start experiementing by rebuilding one of the problem letters and see what happens. Or would it be better to use that dispicable MS Word program for the letters, presuming one could use exported fileds in the way I want (some involve conditionals)?
Ray Lyons
Then 2 things happened: I moved the app to v5 and some network workstations (not all) went to Win2k.
This resulted in some text related to fields printing very small and in some cases overprinting of correctly sized text (one line on top of another). Using win98se I cured all this by simply making a small edit in the rtf (anything, even putting in a zero) and then saving the payout under v5.
But this still did not cure all the problems if a user was using w2k with the very same printer (but of course the printer drivers are different in the differernt OSs). I then determined that Using a w2k machine for development I could cure most of the problems by going into the rtf, selecting all text (including the fields) and making a small change to font or the font size and then saving the layout.
This cured all the overprinting and most of the changes to tiny print--but not all. In some cases, usually where a field is involved (such as an address) the print is still very tiny. That is, tiny when printed under w2k but it shows the correct size in the layout and it still prints correctly under win98se to the very same printer!
I would hate to have to rebuild all the layouts in v5 as there are many of them and most of them are not simple. Any ideas as to what is going on and a cure that does not require rebuilding everything from scratch?
Barring any good ideas, I guess I will start experiementing by rebuilding one of the problem letters and see what happens. Or would it be better to use that dispicable MS Word program for the letters, presuming one could use exported fileds in the way I want (some involve conditionals)?
Ray Lyons
Comment