Good to know, since I'm about to start writing a series of
articles on interfacing with the web. That'll save me some
experimenting!
I recently implemented the web browser control in an A97 app, and it
works great now. But I had a helluva time with it. Here's the thread
where I discussed all the problems (all on one line):
"Problem with keyboard input being locked in a form"
http://groups.google.com/group/microsoft.public.access/browse_thread/
thread/cb33fbaa23b342bb/
I eventually diagnosed that the stealing focus problem was caused by
embedding the control in a subform, because putting it directly on
the tab controlled worked just fine. Obviously, something is broken
in the tab controls ability to interact with an Access subform. It
may be that it can be worked around by doing something with the
controls events, but I didn't delve any deeper. If I needed to embed
it in a subform, I'd definitely look at the events associated with
departure from the control to see if I could set the focus in code
to a native Access control.