I'm having the same problem, and I haven't been able to find an answer either. The following code demonstrates the problem without using PAMIE:
...
I've spent the past couple days working on this problem independently - I discovered it just a few days ago when I returned to some scripts I had written to do website testing. I hadn't used them for a couple months.
The problem seems to be more general than just using fireEvent - document.createEventObject() fails with the same error.
I am running Win2k, and I see the same problem. Being a curious guy, I backed out a few patches to IE, and find that after I uninstall windows hotfix 889293 and 834707, I can fireEvent() and createEventObject() without any problem. But it's not a very good idea to be running without these security updates.
So it seems to me that Microsoft managed to break automation of IE in a pretty bad way. The only documented change I can see that might have caused this is http://support.microsoft.com/kb/887741
I have no idea how to get this fixed - it appears to be either a bug introduced by Microsoft, or a design change. It does make automated web site testing pretty much impossible, unfortunately!
Steve Davis
_______________________________________________ Python-win32 mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/python-win32
