>>>>>Hi,
>>>>>The following snippet is from long-standing code in the Click event of an instance of the _hyperlinklabel class in _hyperlink.vcx:

DODEFAULT()  && Just 'Follow'
>>>>>WITH THIS.oHyperLink.oIE
>>>>>  DO WHILE .busy
>>>>>  ENDDO
>>>>>  IF TYPE(".Document")="O" .AND. !ISNULL(.DOCUMENT.ALL("TextBox2"))
>>>>>    * Code gets to here. Next line errors 'OLE error.  Access Denied'
>>>>>    .DOCUMENT.ALL("TextBox2").VALUE = THISFORM.cKeyToPass
>>>>>  ENDIF
>>>>> ENDWITH

TextBox2 is just asp:TextBox:

<asp:TextBox ID="TextBox2" runat="server"  Style="text-transform:uppercase"></asp:TextBox>

>>>>>
>>>>>Used to work. Something obviously changed but don't know what. Anyone know why this might fail (my VFP is so rusty I may be missing something simple....)
>>>>
>>>>What is the exact error
>>>The usual : "1426: OLE Error 0x80070005: Access is denied"
>>>
>>>>and which IE version you're using?
>>>IE8 (8.0.6001.18702 to be exact).
>>>
>>>>Most likely IE tighted its security model to prevent such automation.
>>> I was wondering about that. If it is an IE security setting then a whole section will have to be rehashed to bypass the problem :-{
>>>
>>>Oh - and I just tested *reading* the value and got the same error
>>
>>I've run into security issues with things like this. You can shut off the check inside of IE:
>>
>>Go to Tools > Internet Options > Security - uncheck the "Enable Protected Mode" and save, then close IE.
>
>Did you miss a step there - there's no 'Enable Protected Mode' at that stage. Is it something under 'Custom Level' ?
>But, given that I could configure IE to bypass the problem on my machine, getting 3000+ users to perform the same operation is not going to be a viable solution :-{



Check the picture.