The Web Browser control has some serious focus issues, but you can usually tweak around with things like setting focus to it and off like you're doing. In some instances you may have to capture the Window events properly (with BINDEVENT()) and that allows to make it work properly without direct hacks, but it's still ugly.

Keep in mind that when ever you reload the page all changes to the page are lost including anything that you've done to the controls unless you simplyh modify the HTML document.

+++ Rick ---

>Ok, I may have found a workaround. It seems that if the browser control has focus when I click the Previous navigation button to move to the Previous record (which rebuilds the HTML content of the control), then the control is enabled despite the Enabled property being set to False. So I tried taking focus off the control before changing records and that resulted in the browser being enabled and disabled correctly. I had done that interactively, so I switched to doing it programmatically and I'm seemingly getting the correct behavior now.
>
>>I have a web browser control on a form. I need to disable it in certain circumstances. I used the Enabled property and it seemed to work fine . . . at first blush. The first thing I noticed is that when I went to a record where the control should be disabled and clicked a pulldown, I was able to change it. Then I think I canceled my changes and it went back to the original value. Then I tried to change it again and this time it would not let me change it. Ok, a small oddity I could live with, I figured. Then I went to another record where the control should be enabled. No problem - it was enabled. Then I went back to the record where it should be disabled and it was enabled. I checked the value of the Enabled property right after setting it - via a WAIT WINDOW - and it was set correctly, but was not actually disabled as it should have been. Has anyone seen this (mis)behavior?
>>
>>Thanks,
>>
>>Russell Campbell