> Hi,
>
[quoted text clipped - 4 lines]
> activated UAC?
> Christian
Yes.
Do a google search in microsoft.public.vb.general.discussion for "Vista",
alternately subkeys "UAC", "OCX", "DLL", ...
If you post again you might be more descriptive on what "problems". <g>
-ralph
Christian Havel - 08 Feb 2008 14:48 GMT
Hi Ralph,
thanks for your response.
My control contains a multiline textbox and some subcontrols, which contains
a label and a textbox. If the user is in the multiline textbox on the POS1
and press the enter buttton, the cursor jumps between the subcontrols for
about 30 seconds.
The OCX is embedded in a VC++ 6.0 MFC dialog.
Christian
> > Hi,
> >
[quoted text clipped - 14 lines]
>
> -ralph
Ralph - 08 Feb 2008 15:27 GMT
> Hi Ralph,
>
[quoted text clipped - 6 lines]
> The OCX is embedded in a VC++ 6.0 MFC dialog.
> Christian
<snipped>
Sorry, I assumed you were using VB. This is a VB newsgroup. I'm not aware of
any reported problems of that nature with VB and the UAC.
I suggest you repost to a VC++ newsgroup.
microsoft.public.vc.mfc or even cross-post to microsoft.public.vc.atl
(depending on what the OCX is written in.).
In the meantime I suggest you take a long look at the message loop. A pure
guess is that the OCX is encountering a permissions issue (UAC essentially
remaps how COM gets resolved) and the error is somehow being swallowed, but
raising misleading or spurious events. The fact it is self-correcting
suggests that if you find the initial error point - the solution will become
obvious. That should give you hope. <g>
-ralph
Christian Havel - 11 Feb 2008 07:38 GMT
Hi Ralph,
der OCX is programmed in VB6. Only the container is a VC++ app.
Christian
> > Hi Ralph,
> >
[quoted text clipped - 25 lines]
>
> -ralph
Ralph - 11 Feb 2008 14:38 GMT
> Hi Ralph,
>
> der OCX is programmed in VB6. Only the container is a VC++ app.
> Christian
If you have Visual Studio/Visual Basic. Then I would create a quick VB app
to use the OCX and see if you experience the same problem.
-ralph