Vernon,
I tested and it worked like a charm. Thank you for helping me dispatch that
headache so quickly.
Ed
From: Vernon D. Cole [mailto:vernondc...@gmail.com]
Sent: Wednesday, September 10, 2014 12:52 PM
To: Irwin, Edward
Cc: python-win32@python.org
Subject: Re: [python-win32] Build 219
Dear Edward:
I feel your pain. The whole idea of including adodbapi as part of
pywin32 was to eliminate having to download and install it as a separate
product. Having it broken in this release sadly means a trip back in time
to the bad old days. Here are the steps I took to attempt to
Vernon,
Any update on a new compiled version of pywin that includes all the adodbapi
components?
If not, how should I go about making my system work? I want to document the
exact steps so our sys admin can replicate on other systems that are running
PyWin. So far I have identified that
Arrgh! You are quite correct.
After completely removing and re-installing python 3.4, I get exactly the
same result. It would appear that my changes in the layout of adodbapi were
not updated in pywin32's distribution setup, but that error was masked in
my testing by pre-existing files on my
Am 29.05.2014 11:33, schrieb Vernon D. Cole:
(if you have pip installed)
pip install adodbapi --upgrade
Worked, thank you very much. This looks as if I could install adodbapi
without the rest of the windows extensions - right or wrong?
Greetings,
Sibylle
Ado is called using COM. adodbapi makes heavy use of the COM interface
capabilities of pywin32 when running on CPython, or the built-in COM
interface on IronPython. It requires one of the two.
On Thu, May 29, 2014 at 11:02 AM, Sibylle Koczian nulla.epist...@web.dewrote:
Am 29.05.2014 11:33,
Hello,
I just installed Python 3.4.1 and pywin32, using
pywin32-219.win-amd64-py3.4.exe. No problems, no error messages during
installation.
When I try to use adodbapi, I get an ImportError:
Python 3.4.1 (v3.4.1:c0e311e010fc, May 18 2014, 10:45:13) [MSC v.1600 64
bit (AMD64)] on win32
