By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,460 Members | 2,215 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,460 IT Pros & Developers. It's quick & easy.

FontName = "Franklin Gothic Medium, Tahoma" ?

P: n/a
It seems the Access 97 FontName property supports multiple font names, e.g.
"Franklin Gothic Medium, Tahoma".

I assume that means that if the first font is not available on the target
PC, the second font will be displayed. Correct?

Also what happens if the font is specified as Franklin Gothic Medium only
and that font is not available on the target PC? Will Access default to some
other font? If so, which one?

TIA
Mark

Nov 12 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
On Mon, 6 Oct 2003 13:24:44 +1300, "Mark B" <remove_from
_h*********************@ihug.co.nz> wrote:

I'm not sure that's entirely true.
For example:
MS Sans Serif,Courier New
and
Courier New,MS Sans Serif
both result in a MS Sans Serif font.

If a font is not available on the target machine, I would presume the
GDI Font Mapper kicks in and retrieves the closest matching font,
based on font characteristics like font family, serif or not, size,
etc.

-Tom.

It seems the Access 97 FontName property supports multiple font names, e.g.
"Franklin Gothic Medium, Tahoma".

I assume that means that if the first font is not available on the target
PC, the second font will be displayed. Correct?

Also what happens if the font is specified as Franklin Gothic Medium only
and that font is not available on the target PC? Will Access default to some
other font? If so, which one?

TIA
Mark


Nov 12 '05 #2

P: n/a
Yeah, therefore makes you wonder why the FontName property does accept two
fonts.

"Tom van Stiphout" <to*****@no.spam.cox.net> wrote in message
news:ft********************************@4ax.com...
On Mon, 6 Oct 2003 13:24:44 +1300, "Mark B" <remove_from
_h*********************@ihug.co.nz> wrote:

I'm not sure that's entirely true.
For example:
MS Sans Serif,Courier New
and
Courier New,MS Sans Serif
both result in a MS Sans Serif font.

If a font is not available on the target machine, I would presume the
GDI Font Mapper kicks in and retrieves the closest matching font,
based on font characteristics like font family, serif or not, size,
etc.

-Tom.

It seems the Access 97 FontName property supports multiple font names, e.g."Franklin Gothic Medium, Tahoma".

I assume that means that if the first font is not available on the target
PC, the second font will be displayed. Correct?

Also what happens if the font is specified as Franklin Gothic Medium only
and that font is not available on the target PC? Will Access default to someother font? If so, which one?

TIA
Mark

Nov 12 '05 #3

P: n/a
Ought to be pretty easy to test... try two very dissimlar fonts, say Arial
and an Old English style, then change the name of the first one,
temporarily. See if it displays the second one, or a mapped font.

Larry Linson
Microsoft Access MVP

"Mark B" <remove_from _h*********************@ihug.co.nz> wrote in message
news:bl**********@lust.ihug.co.nz...
Yeah, therefore makes you wonder why the FontName property does accept two
fonts.

"Tom van Stiphout" <to*****@no.spam.cox.net> wrote in message
news:ft********************************@4ax.com...
On Mon, 6 Oct 2003 13:24:44 +1300, "Mark B" <remove_from
_h*********************@ihug.co.nz> wrote:

I'm not sure that's entirely true.
For example:
MS Sans Serif,Courier New
and
Courier New,MS Sans Serif
both result in a MS Sans Serif font.

If a font is not available on the target machine, I would presume the
GDI Font Mapper kicks in and retrieves the closest matching font,
based on font characteristics like font family, serif or not, size,
etc.

-Tom.

It seems the Access 97 FontName property supports multiple font names, e.g."Franklin Gothic Medium, Tahoma".

I assume that means that if the first font is not available on the targetPC, the second font will be displayed. Correct?

Also what happens if the font is specified as Franklin Gothic Medium onlyand that font is not available on the target PC? Will Access default to someother font? If so, which one?

TIA
Mark


Nov 12 '05 #4

P: n/a
Oh I think what is happening is that it takes the string:

"Old English, Ariel" as being one font name which doesn't exist, so it
defaults back to MS Sans Serif. So it doesn't accept 2 fonts after all....
"Larry Linson" <bo*****@localhost.net> wrote in message
news:sc*******************@nwrddc03.gnilink.net...
Ought to be pretty easy to test... try two very dissimlar fonts, say Arial
and an Old English style, then change the name of the first one,
temporarily. See if it displays the second one, or a mapped font.

Larry Linson
Microsoft Access MVP

"Mark B" <remove_from _h*********************@ihug.co.nz> wrote in message
news:bl**********@lust.ihug.co.nz...
Yeah, therefore makes you wonder why the FontName property does accept two
fonts.

"Tom van Stiphout" <to*****@no.spam.cox.net> wrote in message
news:ft********************************@4ax.com...
On Mon, 6 Oct 2003 13:24:44 +1300, "Mark B" <remove_from
_h*********************@ihug.co.nz> wrote:

I'm not sure that's entirely true.
For example:
MS Sans Serif,Courier New
and
Courier New,MS Sans Serif
both result in a MS Sans Serif font.

If a font is not available on the target machine, I would presume the
GDI Font Mapper kicks in and retrieves the closest matching font,
based on font characteristics like font family, serif or not, size,
etc.

-Tom.
>It seems the Access 97 FontName property supports multiple font
names, e.g.
>"Franklin Gothic Medium, Tahoma".
>
>I assume that means that if the first font is not available on the target >PC, the second font will be displayed. Correct?
>
>Also what happens if the font is specified as Franklin Gothic Medium only >and that font is not available on the target PC? Will Access default

to some
>other font? If so, which one?
>
>TIA
>Mark
>
>



Nov 12 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.