Issues accessing SAGE MAS 200 using a SQL Server dblink

I am having issue accessing any MAS 200 tables via SQL SERVER dblink. MAS 200 client is installed on the same server.
I set up an ODBC on the same SQL Server that is pointing to SAGE MAS 200 database. The ODBC works because I can successfully read the tables via Access.
When I try to set up the dblink on SQL SERVER to MAS 200 it is successful. This is the code I've used:

EXEC sp_addlinkedserver
   @server = 'lnkMAS200TEST',
   @provider = 'MSDASQL',
   @srvproduct='MAS 90 4.0 ODBC Driver',

EXEC master.dbo.sp_addlinkedsrvlogin
    @useself=N'true',   --tried either true or false same result
    @rmtuser= --my MAS 200 Username
     @rmtpassword= --my MAS 200 Password

exec sp_tables_ex 'lnkMAS200Test'   --> this works, successfully returns all tables.

This instead is failing (AP_Division is one of the table returned by sp above):

select * from OPENQUERY(lnkMAS200Test, 'SELECT * FROM AP_Division')

This is the error:

OLE DB provider "MSDASQL" for linked server "lnkMAS200Test" returned message "[ProvideX][ODBC Driver][FILEIO]Table is not accessible".
Msg 7321, Level 16, State 2, Line 1
An error occurred while preparing the query "SELECT * FROM AP_Division" for execution against OLE DB provider "MSDASQL" for linked server "lnkMAS200Test".

I appreciate any help on this one, since I don't know what else to try. I read it could be a permission issue but I tried to log in on the SQL Server into MAS 200 (it is installed) via either the account specified above as security or the sql server service account, both works.

Thank you!
Claudia CarlottiIT DirectorAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Claudia CarlottiIT DirectorAuthor Commented:
I found the issue. I just had to log in as sa in sqlserver not with my personal windows account.
I don't undertand the difference since both the administrative sql account and my personal account are administrators, but this made the difference. I am writing the solution for next person who is reading. Thanks.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Claudia CarlottiIT DirectorAuthor Commented:
just it worked
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2005

From novice to tech pro — start learning today.