The Win API call SetWinPos I used for "Always On Top" does not seem to
function the same in Windows95/VB4 than Win3.11/VB3.  Can anyone help
me with some sample VB4 code to accomplish this function for a form
(and of course the antidote)

Thanks in anticipation.
David Kuchmar

32-bit app, you need the 32-bit Declare:

Declare Function SetWindowPos Lib "User32" (ByVal hWnd As Long, ByVal
hWndInsertAfter As Long, ByVal X As Long, ByVal Y As Long, ByVal CX As
Long, ByVal CY As Long, ByVal wFlags As Long) As Long

Simple, huh!

--
<:) Jeff Law
DataMasta Limited, Mt Maunganui, NZ

: The Win API call SetWinPos I used for "Always On Top" does not seem to
: function the same in Windows95/VB4 than Win3.11/VB3.  Can anyone help
: me with some sample VB4 code to accomplish this function for a form
: (and of course the antidote)
:
: Thanks in anticipation.
: David Kuchmar
:
     I found that my AOT form would no longer be AOT if I put a second
AOT form on it (if I moved the MS Clock on to it, and then off again, for
instance).  This only occured in the VB4 editing environment tho.  AFter
I compiled it and ran the EXE it behaved properly even after being
overlapped by the Clock.  

     I burned a couple of hours chasing this problem in the environment
though (grumble!).

     And goddam GetFocus() is a disaster in NT.  (btw)  I forgot to
update that call in one part of my code and I had radio-buttons jumping
higgley-piggley all over the damn form.  harumph.