Unicode Controls on Forms

  • Thread starter Thread starter Robert Morley
  • Start date Start date
R

Robert Morley

Hi everyone,

I don't usually monitor this group, but I have a forms question, so here I
am. :)

I needed to put a checkmark on a form a while back, and I remember the
controls I was using in Access (2000 or 2002, not sure) not supporting
Unicode characters, so I had to resort to the MT-Sorts font, and distribute
it, and so forth. Playing around in Access 2003, I see that it does support
Unicode characters, and I can use the more widely-available Arial Unicode
checkmark.

Does anybody know for certain when Unicode support was added? If I'm using
2003 to design my form, with the ADP in 2002/2003 format, will 2002 users
see the checkmark correctly?



Thanks,
Rob
 
IIRC, Unicode support was added in Access 2000. You sure you weren't using
Access 97 before?
 
I don't *think* so, but it's possible, as this project originally started
out in A97.

As long as 2002 supports it, that's all I really need to know, but I'd kind
of like to pin it down, just in case it ever comes up again.

Tangentially related to this, I also seem to remember some kind of alternate
font setting or something, to support another code page...was that A97 or
A2000 that had that? I looked through the options in A2003, and I didn't
see it, unless I just missed it. The reason this came up is that I noticed
that switching the font for that same label to Arial or Times New Roman, the
checkmark got drawn (in a different font, mind you), even though those fonts
don't support that character. How does Access decide which font to use? It
certainly didn't use the Arial Unicode font in place of Arial, like you
might expect.



Rob
 
I suspect that it may actually be the version of Windows that is the issue
here, Robert, and not the version of Access at all.

Support for the storage of data using Unicode was added to JET 4.0 and
Access 2000. I have never heard of any other kind of support for Unicode
being added to, or required by, Access.

I could, of course, be wrong, but I *think* you will find that if all your
users are using Access 2000 or later and Windows 2000 or later, you won't
have a problem.
 
Back
Top