riktek
Member
- Local time
- Today, 03:38
- Joined
- Dec 15, 2023
- Messages
- 124
I observed the same behavior in A2007 several years ago and while some weren't able to replicate it, others then confirmed it to be a bug across many Access versions (A2007-A2013) that actually destabilized Access. Today, it manifested in A2019.
To review, we all know that an ampersand (&) in a Caption property designates the immediately following letter as the accelerator key for that object. This is true for Page.Caption (for TabControl pages), specifically.
The problem, which manifested again today on a form that had not previously exhibited it, is that including an ampersand in Page.Caption right-justifies the caption text in the page's tab. Removing the ampersand re-centers the caption text on the tab.
I recall having seen in passing since my initial post, a comment somewhere to the effect that the Caption property for Page objects somehow required special, unique configuration notwithstanding its documentation being indistinguishable from that of other objects' Caption properties. I recall having bookmarked the comment expressly but now can't find it.
I wonder who else is aware of this bug, what its cause or the/a fix might be, and in particular whether anyone is aware of the ephemerally, long-ago noted special handling for Page.Caption that somehow fixes this. I'd be most grateful for any/all constructive input.
To review, we all know that an ampersand (&) in a Caption property designates the immediately following letter as the accelerator key for that object. This is true for Page.Caption (for TabControl pages), specifically.
The problem, which manifested again today on a form that had not previously exhibited it, is that including an ampersand in Page.Caption right-justifies the caption text in the page's tab. Removing the ampersand re-centers the caption text on the tab.
I recall having seen in passing since my initial post, a comment somewhere to the effect that the Caption property for Page objects somehow required special, unique configuration notwithstanding its documentation being indistinguishable from that of other objects' Caption properties. I recall having bookmarked the comment expressly but now can't find it.
I wonder who else is aware of this bug, what its cause or the/a fix might be, and in particular whether anyone is aware of the ephemerally, long-ago noted special handling for Page.Caption that somehow fixes this. I'd be most grateful for any/all constructive input.