My favorites | Sign in
Project Home Downloads Wiki Issues Source
New issue   Search
  Advanced search   Search tips   Subscriptions
Issue 59: Sage Line 100 problems (4GL Retrieve)
1 person starred this issue and may be notified of changes. Back to list
Status:  Investigating
Owner:  ----

Sign in to add a comment
Reported by, Jul 2, 2009
What steps will reproduce the problem?
1. Sage Line 100 (Retrieve Database)
2. Import pyodbc
3. cnxn = pyodbc.connect('DRIVER={Sage Line 

What is the expected output? What do you see instead?
Expected output > Connection Established

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
pyodbc.Error: ('28000', "[28000] Invalid Logon Path (0) 
(SQLDriverConnectW); [01
000] The driver returned invalid (or failed to return) SQL_DRIVER_ODBC_VER: 
 (444); [01000] [Microsoft][ODBC Driver Manager] The driver doesn't support 
version of ODBC behavior that the application requested (see 
SQLSetEnvAttr). (0)
>>> cnxn = pyodbc.connect('DRIVER={Sage Line 

What version of the product are you using? On what operating system?
Python 2.6, latest pyodbc, Windows XP

Please provide any additional information below.
If anyone recognises what could be the problem here please help, I can 
connect to the database through the ODBC within Excel without problems so 
all the data / schema /login paths should be correct!

Jul 3, 2009
Project Member #1 mkleehammer
pyodbc is written against ODBC 3.x (maybe even 3.1).  It looks like the Sage driver
might be older.  Can you find the version of the driver and see what ODBC version it
works with?
Status: Investigating
Jul 4, 2009
It seems that the Sage Line 100 system uses ODBC v2 - it's not surprising that it 
uses an early version since it's DOS based but until my company upgrade to some more 
modern ERP or I find some way to talk to it it will continue to accommodate their 
business needs.

Am I right in thinking there isn't an earlier version of pyodbc that would support 

Many thanks for the response

Jul 15, 2009
Project Member #4 mkleehammer
You are correct.

The ODBC driver manager will convert most ODBC 3 calls on the fly to ODBC 2 ones. 
Anything added to 3, however, will obviously fail.  If you *really* need ODBC 2
support and want to do some dev/testing yourself, you might be able to identify the
different calls and we can wrap them with #ifndef ODBC2 or something like that. 

I wish I could do more.  Have you confirmed that a newer driver isn't available?  You
may be able to get a newer driver that talks to an older backend.
Sign in to add a comment

Powered by Google Project Hosting