Determine Windows XP Style or Windows Classic Style

[Lauren Quantrell]

In Windows XP display Properties/Appearance users can chose between:
Windows XP Style or Windows Classic Style.

Is there a way in VBA to determine the user's selection?

The reason:

Toolbars size taller in XP than in Classic so I need to size all those
nifty windows sizing commands depending on the user's preference.

Any help is appreciated.
lq

[lylefair]

Sigh!

[Lauren Quantrell]

Ouch. I've been "Lyle-Sighed".
Is this because the question is incredibly inept or because there is
such an obvious solution, or maybe you just haven't sighed lately?
lq

[Lauren Quantrell]

Thatnks for the sigh - you inspired me to dig further and he answer was
right under my nose and your Sigh suggested:
http://support.microsoft.com/?kbid=210603

[lylefair]

Then I am prouder of my "Sigh" than of any other contribution I have
made to CDMA, ever.

[DFS]

Lauren Quantrell wrote:

In Windows XP display Properties/Appearance users can chose between:
Windows XP Style or Windows Classic Style.

Is there a way in VBA to determine the user's selection?

The reason:

Toolbars size taller in XP than in Classic so I need to size all those
nifty windows sizing commands depending on the user's preference.

Any help is appreciated.
lq

I was thinking about this very issue the past week, but the problem is the
difference is 1/4 an inch or so, and I would have to size all the controls
along with the form.

Let us know what you do with this.

Thanks

[Lauren Quantrell]

DFS:
This is what I came up with.
I hope this helps.
' the following items used for GetSystemMetric s: (put in code module)
Private Declare Function GetSystemMetric s Lib "user32" _
(ByVal nIndex As Long) As Long

Private Const SM_CYSIZE = 31 ' Height of bitmaps in title bar

Function MenuHeight() As Long
On Error Resume Next
' Measure the height of the application menu bar
MenuHeight = GetSystemMetric s(SM_CYSIZE)
End Function
Function SomeFunctionTha tResizesThings ()

Dim myMenuHeight As Long, cH as Long

' measure the windows title menu height: _
returns 18 Windows Classic Mode / 25 Windows XP Mode

myMenuHeight = MenuHeight

' size my window height: (36 is the height of a toolbar, used as an
example)
cH = 36 + myMenuHeight

End Function

' Another approcah to this using a boolean value to _
determine if XP or Classic Theme is in use:

Function IsXPStyle() As Boolean
On Error Resume Next
' Determine if XP Syle is in use
IsXPStyle = (CLng(GetSystem Metrics(SM_CYSI ZE)) >= 25)
End Function

[David W. Fenton]

"Lauren Quantrell" <la************ *@hotmail.com> wrote in
news:11******** *************@g 47g2000cwa.goog legroups.com:

In Windows XP display Properties/Appearance users can chose
between: Windows XP Style or Windows Classic Style.

Is there a way in VBA to determine the user's selection?

The reason:

Toolbars size taller in XP than in Classic so I need to size all
those nifty windows sizing commands depending on the user's
preference.

Why is it that just finding the size of the Access MDI client window
is insufficiont, since it excludes the toolbars? The window sizing
class on the Access Web includes code for getting the size of the
Access MDI client window.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Lauren Quantrell]

The object here is to size the overall Access window to a fixed height,
including the Windows title bar plus any maximized (non popup) form it
may contain.
lq

[David W. Fenton]

"Lauren Quantrell" <la************ *@hotmail.com> wrote in
news:11******** **************@ f14g2000cwb.goo glegroups.com:

The object here is to size the overall Access window to a fixed
height, including the Windows title bar plus any maximized (non
popup) form it may contain.

Um, why?

I hate running programs like Access non-minimized. Web browsers I
run non-minimized, but almost all other apps I want taking up the
whole screen. An app that is designed to override my choices will be
one I will not like using.

Of course, you're not designing for me.

But I've also found that my non-techie clients function better with
maximized applications than with non-maximimzed, because they always
end up missing part of the information onscreen (especially in
Access, where the forms don't dynamically resize unless you
incorporate complex form resizing code that makes your forms look
pretty ugly in certain sitautions, and doesn't really deal with the
problem that occurs when the parent window is not big enough to
display the entire form). I've observed them lose things and scroll
around unnecessarily, problems that wouldn't occur at all if they'd
only run the parent app maximized.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc