On Sun, Feb 25, 2018 at 6:18 PM, Mark Hammond wrote:
> 1) There's a relatively easy fix that can be made to the copy of adodbapi
> which is inside pywin32.
Right. Basically, I think what needs to happen is for the fork on
GitHub to be brought in sync with the working
Hi all,
I'm happy to announce the release of pywin32 build 223.
The only significant change in this release is to help pywin32 when
being installed as a wheel (ie, via pypi) - the pywin32_system32
directory is now added to PATH. Thanks to @xoviat via
On 26/02/2018 1:12 am, Bob Kline wrote:
On Sun, Feb 25, 2018 at 12:31 AM, Mark Hammond
wrote:
I'm afraid Bob is going to get quite frustrated if he gets upset about
responses taking more than a few days to come in.
I'm going to assume you hadn't yet read the
On Sun, Feb 25, 2018 at 12:04 PM, Preston Landers wrote:
> Is there [any] reason you can't use PyODBC?
A reasonable question. This is not for a new project. When it was
first started the analysis of the available options for database
connection libraries came to the
Bob,
Is there are reason you can't use PyODBC?
https://github.com/mkleehammer/pyodbc/wiki
It is more actively maintained and I've used it successfully for years.
I'm curious what adodbapi is doing for you that PyODBC can't? Are you using
non-SQL data sources?
thanks,
Preston
On Sun, Feb 25, 2018 at 12:31 AM, Mark Hammond
wrote:
> I'm afraid Bob is going to get quite frustrated if he gets upset about
> responses taking more than a few days to come in.
I'm going to assume you hadn't yet read the thread leading up to
Vernon's last message.