Corrupt mxODBC installation?

[Jose Correia]

Hi Marc-Andre,

Thanks for replying.

 Marc-Andre Lemburg wrote:
> Could it be that Python is still picking up some not 100%
> uninstalled version of mxODBC on the machine ?
>
> Try running Python in verbose mode to have it print out the
> paths it tries for finding the modules:
>
> python -vv

Did that, all looks ok to me.  relevant bit of the output:
=== START line 289 of output file ===
# trying mx.pyd
# trying mx.dll
# trying mx.py
# trying mx.pyw
# trying mx.pyc
# trying D:\Python\lib\site-packages\Pythonwin\mx.pyd
# trying D:\Python\lib\site-packages\Pythonwin\mx.dll
# trying D:\Python\lib\site-packages\Pythonwin\mx.py
# trying D:\Python\lib\site-packages\Pythonwin\mx.pyw
# trying D:\Python\lib\site-packages\Pythonwin\mx.pyc
# trying D:\Python\lib\site-packages\win32\mx.pyd
# trying D:\Python\lib\site-packages\win32\mx.dll
# trying D:\Python\lib\site-packages\win32\mx.py
# trying D:\Python\lib\site-packages\win32\mx.pyw
# trying D:\Python\lib\site-packages\win32\mx.pyc
# trying D:\Python\lib\site-packages\win32\lib\mx.pyd
# trying D:\Python\lib\site-packages\win32\lib\mx.dll
# trying D:\Python\lib\site-packages\win32\lib\mx.py
# trying D:\Python\lib\site-packages\win32\lib\mx.pyw
# trying D:\Python\lib\site-packages\win32\lib\mx.pyc
import mx # directory D:\Python\lib\site-packages\mx
# trying D:\Python\lib\site-packages\mx\__init__.pyd
# trying D:\Python\lib\site-packages\mx\__init__.dll
# trying D:\Python\lib\site-packages\mx\__init__.py
# D:\Python\lib\site-packages\mx\__init__.pyc matches
D:\Python\lib\site-packages\mx\__init__.py
import mx # precompiled from D:\Python\lib\site-packages\mx\__init__.pyc
import mx.ODBC # directory D:\Python\lib\site-packages\mx\ODBC
# trying D:\Python\lib\site-packages\mx\ODBC\__init__.pyd
# trying D:\Python\lib\site-packages\mx\ODBC\__init__.dll
# trying D:\Python\lib\site-packages\mx\ODBC\__init__.py
# D:\Python\lib\site-packages\mx\ODBC\__init__.pyc matches
D:\Python\lib\site-packages\mx\ODBC\__init__.py
import mx.ODBC # precompiled from
D:\Python\lib\site-packages\mx\ODBC\__init__.pyc
import mx.ODBC.Windows # directory
D:\Python\lib\site-packages\mx\ODBC\Windows
# trying D:\Python\lib\site-packages\mx\ODBC\Windows\__init__.pyd
# trying D:\Python\lib\site-packages\mx\ODBC\Windows\__init__.dll
# trying D:\Python\lib\site-packages\mx\ODBC\Windows\__init__.py
# D:\Python\lib\site-packages\mx\ODBC\Windows\__init__.pyc matches
D:\Python\lib\site-packages\mx\ODBC\Windows\__init__.py
import mx.ODBC.Windows # precompiled from
D:\Python\lib\site-packages\mx\ODBC\Windows\__init__.pyc
Traceback (most recent call last):
  File "testmx.py", line 3, in ?
    dbc = mx.ODBC.Windows.Connect("TradeHive32", user="", password = "",
clear_auto_commit = 0)
AttributeError: 'module' object has no attribute 'Connect'
==== END  line 327 of output file (total length 937)========


> Versions prior to mxODBC 2.0 are no longer available on the web.
> The egenix-mx-commercial Windows installers are around 196kB in
> size, so the size you reported looks odd.

Sorry my mistake (typo) the files are as follows (downloaded both 3 times
now from your site):
12-20-01  20:38 591,644 egenix-mx-base-2.0.3.win32-py2.2.exe
01-11-02  14:31 197,293 egenix-mx-commercial-2.0.4.win32-py2.2.exe

I've un-installed and re-installed them several times (base file 1st) but
still no luck.  I've also uninstalled and re-installed Python (and renamed
odbc.pyd in win32 just in case).

You mention you keep the base and odbc files in sync.  Grasping at straws,
could the fact that one is 2.0.3 and the other 2.0.4 have anything to do
with it?

Appreciate your input.

Jose