[DB-SIG] Acessing DBISAM files via mxODBC

M.-A. Lemburg mal@lemburg.com
Mon, 12 Feb 2001 10:48:46 +0100

Kent Tenney wrote:
> Marc-Andre,
> This is the first time I've run from the command line, I was getting
> errors when I ran the cur.execute('SQL...') from the interactive window
> of ActiveState Python.
> It does look like I have a cursor which is hooked to the data OK.

That's what I thought...
> Is it common to get different results from interactive Pythonwin and
> sending a file to python.exe?

Not really, but then the ODBC driver you are using is so buggy
I wouldn't be too surprised (I downloaded it and tried to run
the test.py script on it... failed badly with some really
wild results).

I'd write to the driver's maintainer about this -- in it current
state it is not very useful.

BTW, are you bound to keeping the data in those DBISAM files ?

There are much better quality ODBC drivers which interface to the
MS Jet Engine available from Microsoft (just download and install
their MDAC lib). The Jet engine is the database engine driving 
Access, BTW, and since it's free, I'd suggest taking a look
at it.

Marc-Andre Lemburg
Company:                                        http://www.egenix.com/
Consulting:                                    http://www.lemburg.com/
Python Pages:                           http://www.lemburg.com/python/