I am using Long Text Rich text is fields in a table that appear on a report.
Usually Can grow just works.
However I do have this case where the font is Calibri. The control does not grow. It just stops at what lands as the first line of text. We have tried inserting a line break, ensuring the contol's line spacing is 0" (an issue I saw for an Access 2003 user. I am using 2016).
A few noteworthy things. Changing the font to Arial works.
If I use CSTR() in a query on the field so I can see the tags, the face attribute or font name part of the font tag has double quotes around the Arial font but not Calibri. I tried replacing the double quotes into the data but it did not fix the issue either.
Using Calibri (detail) which incidentally does insert double quotes does work. It also looked different in our sample table and the actual table.
Currently the actual table is being recreated hoping there is corruption of some sort. Edit Update(1 of 2): Table recreated and did not solve this issue. It did fix some unusual behavior in the display font vs. selected font for the affected field in the table.
That is what I know any other insights appreciated.
I would like to understand exactly what Calibri (detail) is especially compared to Calibri. Is that an indicator of the theme font or is it something else?
Edit Update (2 of 2): Calibri (Detail) 12 pt vs Calibri 14 pt seems about right (note also bold). This seems to be the workaround.
Usually Can grow just works.
However I do have this case where the font is Calibri. The control does not grow. It just stops at what lands as the first line of text. We have tried inserting a line break, ensuring the contol's line spacing is 0" (an issue I saw for an Access 2003 user. I am using 2016).
A few noteworthy things. Changing the font to Arial works.
If I use CSTR() in a query on the field so I can see the tags, the face attribute or font name part of the font tag has double quotes around the Arial font but not Calibri. I tried replacing the double quotes into the data but it did not fix the issue either.
Using Calibri (detail) which incidentally does insert double quotes does work. It also looked different in our sample table and the actual table.
Currently the actual table is being recreated hoping there is corruption of some sort. Edit Update(1 of 2): Table recreated and did not solve this issue. It did fix some unusual behavior in the display font vs. selected font for the affected field in the table.
That is what I know any other insights appreciated.
I would like to understand exactly what Calibri (detail) is especially compared to Calibri. Is that an indicator of the theme font or is it something else?
Edit Update (2 of 2): Calibri (Detail) 12 pt vs Calibri 14 pt seems about right (note also bold). This seems to be the workaround.
