>>>>> "BK" == Bob Kline <[EMAIL PROTECTED]> writes:
>> If you can't fix it, make it worse, and see what you learn... I'd
>> try to break the working account by renaming the module that's
>> failing to load. Do you get the same error message in the currently
>> working account?
BK> No, I get the message "No module named pythoncom" when I do that. The
BK> original problem has "The specified module could not be found." (This
BK> was raised by an attempt to invoke pythoncom.CoCreateInstance()).
OK, that's interesting, it's a different error, which makes the source
of the original error intriguing.
Hmmm. Looking at dynamic.py, I see that the error is coming from the
except clause in an exception handler. I'd put a print statement --
printing out the value of IDispatch, what the heck, and maybe clsctx
-- before and after line 70, and also right after the except
statement. Or step through it in a debugger, but printing is cheap
and easy.
Does he not have a server running, and you do, maybe? This might be a
bad error message, they do happen. Or is the error coming from the
server?
Here's the code snippet from dynamic.py, starts at line 67:
def _GetGoodDispatch(IDispatch, clsctx = pythoncom.CLSCTX_SERVER):
if type(IDispatch) in _GoodDispatchType:
try:
IDispatch = pythoncom.connect(IDispatch)
except pythoncom.ole_error:
IDispatch = pythoncom.CoCreateInstance(IDispatch, None,
clsctx, pythoncom.IID_IDispatch)
return IDispatch
--
Patricia J. Hawkins
Hawkins Internet Applications, LLC
_______________________________________________
ActivePython mailing list
[EMAIL PROTECTED]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/ActivePython
