Black font to Red font in line

[Dan_Flynn_(Guest)]

I have a form,(Can e-mail to you to see for yourself if requested and you supply e-mail) has the following format:____28.| 3 | blank blank | 77 |__b r b b b(but shows red)____legend__b: set as black font__r: set as red font____If I put text where blank is shown the 77 red changes to black.____What is causing this?____Thanks__Dan__Dan@megaflex.com__

[kfleming]

This is not a problem that I have seen before.____Kathleen__R&R Support

[DFlynn]

I can send you an example, pdf file where it is shown. This occurs on every form. Send me you email, so I can attach the pdf file.____Dan

[DFlynn]

Send me a private e-mail at Dan@megaflex.com and I will send you a pdf of the red black printing problem. It shows up on all of my forms.____Dan

[Dan_Flynn_(Guest)]

Kathleen,____I mailed you a sample printout showing this problem, but have not heard from you. If you need another copy I can send you email.____Dan

[kfleming]

I have the print out but it does not tell me enough about the contents of the report to be able to explain what is happening.__I would really need the actual report file and some sample data showing the problem to figure this one out.____Kathleen__R&R Support__kfleming@livewarepub.com

[kfleming]

Thanks for sending the files. I have confirmed that it is a bug.____If you have a line on the report where you have a field with a color print attribute and then a field and then a text field, when the second field is empty (so that the text field is the next thing that will print on that line after the color field) the text field takes on the color of the last printed field.____I have found a few ways to get around this.__The first is to add a field to the line whose expression is space(1) and put this field somewhere between the color field and the text field. Another way around is to use a calculated field in place of the text field. So instead of the text 76 you could create a calculated field with the expression "76"____I went back a bunch of releases and this bug has been around at least since Windows Version 6.5 and probably always. Amazing that it has not surfaced until now.______Kathleen__R&R Support