Project Module - extracting data into Excel

[beancounter67]

I need to pull some project data out of Sage 50 v16 to create a bespoke report in Excel. I've looked at the preset Sage extracts and also on the net at tools like WebXel but none of them have anything for the project module.

Can anyone help?

Sara

[leyburnsolutions]

You can use the Sage 50 ODBC to extract the data from Sage into Excel, there are a number of tables that expose the Project data. You can get an idea of what is required by editing the Project reports in Sage which will allow you to see the table/field names.

John

[beancounter67]

Thanks for the info. The problem I have is that I can't find the Sage 50 ODBC driver - it should be in %drive%/windows/system 32 but it's not. I've tried using the ODBC set up routine in %drive%/sage/accounts/ODBC32 but other than telling me the software is installed (Sage Accounts ODBC) I get no further.

I'm guessing Sage 50 v16 ODBC is not the same as Sage Accounts ODBC. How do I get hold of the correct driver?

Sara

[leyburnsolutions]

You should have a System DSN called SageLine50v16 - if reports can be run in Sage then it must be installed as the Report Designer uses the ODBC driver...

John

[beancounter67]

I've looked in the ODBC Administration Tools and can't see the Sage driver - the only one I get the option to add is a SQL Server.

I can definately run reports in Sage, including ones I've amended.

I'm using Sage 50 2010 V16 on Windows 7 - could this combination be the problem?

Sara

[beancounter67]

This is really strange. If I load MS Query, I can see the SageLine50v16 driver (but I get an SQLSetConnectAttr error when I try to open the database), but when I look in ODBC Administration Tools it's not there.

Any ideas?

Sara

[brucedenney]

Could this be a 64 bit edition of Windows 7 that hides 32bit odbc driver?

To setup DSN for 32-bit application you must use:
%WINDIR%\SysWOW64\odbcad32.exe