The ODBC driver for any Sage 100 version is READ ONLY. You cannot pull data into MAS via ADODB.  Now you may hunt around and find the ProvideX Read-Write ODBC driver but DO NOT use it as it will result in 100% data corruption 100% of the time.  The ONLY way to bring data into MAS is with VI or BOI.  Note that if you can write VBA code then you should be able to write code and use BOI to do what you want.

Thanks for the response BigLouie, but please note that I was asking how to pull data from MAS INTO Excel.  (WITHOUT using Microsoft query).

Thanks for the response BigLouie, but please note that I was asking how to pull data from MAS INTO Excel.  (WITHOUT using Microsoft query).

OK now I see. Microsoft query seems to be an integral part of Excel and I don't see a way to pull data without using it.

So you can't pull data into excel using Data --> From Other Sources-->From Data Connection Wizard?

Only Data --> From Other Sources-->From Microsoft Query?

Unless something changed between 4.5 and 2013, it should work.  I use it almost everyday.

Data - From Other Sources - From Microsoft Query

Joe

Edited - Sorry misread your post - I believe you do have to use Microsoft Query. 

OK thanks.  Just going to throw this out there -

What I'm attempting to do is populate a column on a hidden worksheet with a mas vendor list upon opening the workbook.  This column would be the datasource for a validation list of a cell on a visible worksheet.

You should be able to do this with a silent DSN. That is a newly created DSN based on the Sage ODBC driver and with the user log in info included.

I would love for that to work, but it seems like no matter what I try - either using a silent DSN or a non-silent DSN (which would prompt me with a the MAS login screen) - with both 32/64 bit odbc drivers, I get the same 'Could not retrieve list of tables from datasource' message.

Sounds like you should use an Access DB instead of Excel.  It would be more automatic like you are looking for.

I have noticed that the problem seems to occur when the 64 bit version of office is installed, but I don't have the issue with the 32 bit.  I think the ODBC driver is the issue as you are using a 64 bit tool to work through a 32 bit ODBC.