The following code:
conn = win32com.client.Dispatch(r'ADODB.Connection')
DSN = 'PROVIDER=Microsoft.Jet.OLEDB.4.0;DATA SOURCE=%s;Jet
OLEDB:Database Password=root' % dbName
conn.Open(DSN)
gives:
com_error: (-2147352567, 'Exception occurred.', (0,
u'ADODB.Connection', u'Provider cannot be found. It
Hi all,
I've been using the win32com module for a few weeks now and am pretty
amazed about the possibilities.
I want to use it to automate various tasks. However I am afraid of
Microsoft version changes destroying my scripts. Is there any experience
or estimate about this risk (we currently use
Baehr, Manuel wrote:
Hi all,
I've been using the win32com module for a few weeks now and am pretty
amazed about the possibilities.
I want to use it to automate various tasks. However I am afraid of
Microsoft version changes destroying my scripts. Is there any experience
or estimate about
On Tue, Apr 21, 2009 at 3:52 PM, Tim Golden m...@timgolden.me.uk wrote:
Actually I had previously placed a delay between the new_rule creation
and calling AddMembershipRule for another reason -- to make a clear
break in the timestamps on the server side wmi logs. Unfortunately
the delay
John Randolph wrote:
On Tue, Apr 21, 2009 at 3:52 PM, Tim Golden m...@timgolden.me.uk wrote:
Actually I had previously placed a delay between the new_rule creation
and calling AddMembershipRule for another reason -- to make a clear
break in the timestamps on the server side wmi logs.
