text box bullets
- Thread starter y2k
- Start date
Hayley Baxter
Registered User.
- Local time
- Today, 16:57
- Joined
- Dec 11, 2001
- Messages
- 1,607
I could be wrong here but to my knowlege you cannot have bullets in a text box in a report. I know you can do this in a data access page. As I said don't quote me on that. Anyone else?
Hay
Hay
- Local time
- Today, 10:57
- Joined
- Feb 28, 2001
- Messages
- 30,085
You can have bullets in a text box in an Access report. But there is a catch...
You can't have normal text in the same text box unless you can find a True Type Font file that has text and bullet symbols in the same file.
You can use the Windows Character Map application to examine a given font file for this characteristic. If you find a font that has normal text PLUS something you want to use for a bullet, then the text box to contain the bullet must include
chr$(code-for-bullet-symbol) & " " & [datafield]
where you can find the code-for-bullet-symbol through the Character Map accessory.
A further catch - if you sometimes want a bullet and sometimes don't, you need something a bit more complex to record this fact. I.e. you can no longer just add in the prefix of the chr$ function of the symbol code.
Now, there is a sneaky, back-door approach to this, too.
Let's say for the sake of argument that ALL detail records must be bulleted. Then in the design view of the form you could build a label field, reset the font to the Symbols font, and specify the character or code to be used for the bullet symbol. Then you can drag-drop the label next to your raw data, use the justification options to align the bullet, and let 'er rip.
Of course, if even one detail record should not have a bullet, then you need to make more work for yourself because now that bullet doesn't belong there.
Now, the bad news. If you export this report to Word (in .RTF format), bulleted lists aren't bulleted lists any more. The RTF won't necessarily lose the formatting - but Word won't recognize that it is a list. The bullet will look just like any other character, just with a funky character code and parameters.
You can't have normal text in the same text box unless you can find a True Type Font file that has text and bullet symbols in the same file.
You can use the Windows Character Map application to examine a given font file for this characteristic. If you find a font that has normal text PLUS something you want to use for a bullet, then the text box to contain the bullet must include
chr$(code-for-bullet-symbol) & " " & [datafield]
where you can find the code-for-bullet-symbol through the Character Map accessory.
A further catch - if you sometimes want a bullet and sometimes don't, you need something a bit more complex to record this fact. I.e. you can no longer just add in the prefix of the chr$ function of the symbol code.
Now, there is a sneaky, back-door approach to this, too.
Let's say for the sake of argument that ALL detail records must be bulleted. Then in the design view of the form you could build a label field, reset the font to the Symbols font, and specify the character or code to be used for the bullet symbol. Then you can drag-drop the label next to your raw data, use the justification options to align the bullet, and let 'er rip.
Of course, if even one detail record should not have a bullet, then you need to make more work for yourself because now that bullet doesn't belong there.
Now, the bad news. If you export this report to Word (in .RTF format), bulleted lists aren't bulleted lists any more. The RTF won't necessarily lose the formatting - but Word won't recognize that it is a list. The bullet will look just like any other character, just with a funky character code and parameters.
