Sage 2010 ODBC

Posted by jason.raikes PM | on Wed, 02/06/2010 - 11:09 1823 5 comments | report

Hello,

I have been having problems using the Sage 2010 odbc driver (v16). The major issue is that it seems to be tempremental - i.e inconsistent with when it does / does not work properly. I have discovered that the field RECORD_DELETED in the table AUDIT_JOURNAL does not provide consistent data and that opening OLE DB recordsets can be a problem. Anyone else experienced this or have any tips? Also, can anyone tell me whether I have an up to date ODBC driver, my version number is 2.00.00.913.

Regards,

Jason Raikes

www.pendragonsystems.com

Comments

odbc driver version

Christop51 | Wed, 02/06/2010 - 21:11 | Permalink

Hi Jason

I have used odbc links to several versions of Sage and never had any problems.

Regarding the odbc driver, where did you get your version number?

The ODBC driver manager accessed from 'Control Panel' - 'Administrative tools' - 'Data Sources (ODBC)' ('about' tab) on both my Vista Pro and Home premium laptops show as Version 6.0.6002.18005.

ODBC version

jason.raikes | Wed, 02/06/2010 - 22:11 | Permalink

Chris,

Thanks for the reply. The About tab shows the ODBC version, I am interested in the version of the Sage ODBC driver - In the ODBC Data Source Administration tool, click on the Drivers tab and find the entry for Sage Line 50 v16 in the list and the version is in the next columns.

Regards,

Jason Raikes

www.pendragonsystems.com

ODBC

johndon68 | Wed, 02/06/2010 - 23:02 | Permalink

I'm pretty sure that's the latest version of the driver, certainly it's the same as mine and I've got all the current updates installed.

I've got an app that uses OLEDB and I've not come across any issues so far with the 2010 ODBC driver.

John

Sage 50 ODBC driver

tbayliss | Thu, 03/06/2010 - 00:14 | Permalink

The ODBC driver with Sage 50 was developed by a 3rd party and is a bit flaky. Not sure who the 3rd party is/was but I believe Sage do not provide technical support for it to users or resellers. Certainly that was the reply I got last time I tried to help someone who used it. Sage said they were responding to user requests when they had the ODBC driver written for Sage 50. Many users use it, particularly from Excel and Microsoft Access but because Sage did not develop it and as they provide it "free" with Sage 50, they could not help with problems.

They do support the Visual Basic toolkit supplied to Sage Developers that lets you not just read but write to the Sage database but it costs over £300 a quarter to be a Sage Developer. I know as I pay the fee and you do need to know a bit of VB/VBA but it does work much more reliably and far quicker than the ODBC driver - at a price.

ODBC Driver

johndon68 | Thu, 03/06/2010 - 07:30 | Permalink

The ODBC driver is written by Sage themselves. The problem for people using it externally is that it's only reason for being is for the Report Designer in Sage - as a result it does not support all ODBC functions, it supports just enough to be used to generate reports in Sage 50.

Going back to the original issue, you should have more luck if you use the AUDIT_HEADER and AUDIT_SPLIT tables - I use these quite extensively and I've never had an issue with the DELETED_FLAG on those tables.