Subject Re: evaltags in a custom report From Charlie <tm@tc.com> Date Sat, 08 May 2021 09:54:13 -0400 Newsgroups dbase.getting-started OK so the tags are invisible in the text but they function.  For instance (br) causes the next line etc.  My question was is there some sort of a property I can change to make them not function in this particular text component in the report.  Actually if there is a way to get rid of them before they hit the report makes more sense.  So I will try your code in a program leading up to the report.  Now that I understand that they are a problem I can try to eliminate them by program or manually from now on.  Not a big deal now that I understand it is probably not possible in the report. Mervyn Bick Wrote: > On 2021/05/06 19:11, Ken Mayer wrote: > > > Um, if there are HTML tags in the text being displayed they will be > > evaluated as well as the text control is able to. Trust me on this, I > > use them ... > > > > A textLabel control cannot evaluate HTML tags, but text controls can and > > do. > > Duh. Of course they do. Another case of "mind in neutral".  I can't > begin to count the times I've used HTML tags to change the colour of > part of the text on a form. > > That begs the question of why the tags are being evaluated for Charlie > on his form but not in the report. Textlabel controls are available in a > report but if one drags a field from a table to a report the designer > uses a text object. > > Charlie, please confirm that your report uses text rather than textlabel > controls. > > Mervyn >