How can I display extended characters; The Vulgar Fractions

[Ted Stilwell]

I'm using office 97 and would like to use some of the extended characters ?
? ? ? . The character map refers to these as U+215B: Vulgar Fraction one
eighth, . . .U+215E: Vulgar Fraction seven eighths. When I try to use them
in forms or reports I get just the undisplayable character symbol. Is there
a way around this?
Many thanks in advance,
Ted Stilwell

 

[Dirk Goldgar]

I'm using office 97 and would like to use some of the extended
characters ? ? ? ? . The character map refers to these as U+215B:
Vulgar Fraction one eighth, . . .U+215E: Vulgar Fraction seven
eighths. When I try to use them in forms or reports I get just the
undisplayable character symbol. Is there a way around this?

How are you trying to use them? Are you using a font that supports the
Unicode character set? In a text box with its Font property set to
Arial or Tahoma, I can set the text box's value to

ChrW(&H215B)

or

ChrW(8539)

and see the one-eighth character.

 

[Ted Stilwell]

Thanks Dirk,
It's odd! I can see these characters in the character map with several
fonts including Arial & Tahoma and even times new roman but they will not
display in our installation of Access97. Visual basic recognizes the ChrW
function but ChrW is not listed in the expression builder.
'=ChrW(&H215B)' in the control source for a textbox gives invalid syntax
messages but VB recognizes both expressions ChrW(&H215B) & ChrW(8539). i.e.
MsgBox ChrW(8539)
MsgBox ChrW(&H215B)

yields

? (question mark)
? (question mark)

The help file VEenLR.hlp which relates to ChrW is unavailable in our
installation.

Thanks again,
Ted Stilwell

 

[Dirk Goldgar]

Thanks Dirk,
It's odd! I can see these characters in the character map with
several fonts including Arial & Tahoma and even times new roman but
they will not display in our installation of Access97. Visual basic
recognizes the ChrW function but ChrW is not listed in the expression
builder. '=ChrW(&H215B)' in the control source for a textbox gives
invalid syntax messages but VB recognizes both expressions
ChrW(&H215B) & ChrW(8539). i.e. MsgBox ChrW(8539)
MsgBox ChrW(&H215B)

yields

? (question mark)
? (question mark)

The help file VEenLR.hlp which relates to ChrW is unavailable in our
installation.

I'm sorry. I just realized that you're working with Access 97, which
you mentioned in your first post. My tests were done in Access 2002. I
have a sinking feeling that Access 97 doesn't support unicode for text
fields or text controls, although the ChrW function does exist, as
you've noticed. Support for unicode in text fields was added with
Access 2000, though, so it seems likely that unicode support as a whole
was added with the 2000 release.

 

[Brendan Reynolds]

You're right, Dirk, Unicode support was a new feature in Jet 4. About the
ChrW function - I'm not 100% certain of this, but my guess, for whatever
that may be worth, would be that VBA 5 may have supported Unicode, so
expressions that were evaluated by VBA would recognize the function, while
expressions that were evaluated by Access or Jet would not.

 

[Ted Stilwell]

There's just no up side to being a Neanderthal. Thank for your help Dirk
& Brendan.

 

[Dirk Goldgar]

There's just no up side to being a Neanderthal.

You do get those cool brow ridges.

 

[Ted Stilwell]

LSHIH (Laughing So Hard It Hurts)

You do get those cool brow ridges.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)