Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Remote ODBC connection to MAS 90 using .NET

Status
Not open for further replies.

yuu012

Technical User
Jun 12, 2005
3
US
Hi,

I want to connect to MAS90 data source, which is not local but on a different computer.
The driver on the remote machine is ProvideX ODBC Driver version 4.21.1000.
We are using visual studio 2008 and c#.
I tried many different connection strings, for example:

conn.ConnectionString = @"Driver={MAS90 32-Bit ODBC Driver};DSN=SOTAMAS90;User=xxx;Password=xxxx;Company=xxx;Server=xxx.xxx.x.xxx";

conn.ConnectionString = "DSN=SOTAMAS90_KEN2;UID=xxx;PWD=xxxx;Company=xxx;Server=xxx.xxx.x.xxx";

I tried various versions, but I always get "ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified".
Has anyone connected MAS90 data source remotely using .NET?
I really appreciate your information even if your language is not c#, using different version of Visual Studio, or different version of driver.

Thanks in advance.
 
The second one is close, but should be SOTAMAS90 unless you set up your own. Then the Server should be a drive letter or UNC path not an IP address. Plus you're missing all the other stuff after it. If you go into the data source, on the debug tab it will give you the connection string you can use to copy and paste.

Dawn

Visit Sage's Online Community
 
Dfeller,
Thank you for your reply.
I checked the connection string, and I tried with "Directory", "Prefix", "ViewDLL" etc. too.
I created the DSN with the name "SOTAMAS90_KEN2", so, that part is correct.

conn.ConnectionString = @"DSN=SOTAMAS90_KEN2;UID=xxx;PWD=xxxx;Directory=\\xxx\Sage V4\MAS90;Prefix=\\xxx\Sage V4\MAS90\SY\, \\xxx\Sage V4\MAS90\==\;ViewDLL=\\xxx\Sage V4\MAS90\HOME;Company=xxx;RemotePVKIOHost=xxx.xxx.x.xxx;SERVER=NotTheServer";

>"Then the Server should be a drive letter or UNC path not an IP address."
We are logging on to the remote machine using VPN client and remote desktop when we manually log on to data source.
So, I set the RemotePVKIOHost to the IP address of the machine, and set SERVER=NotTheServer, and tried without "SERVER=..." too, but they didn't work.
I guess I cannot use the UNC path because the machine is not on our network. (Actually, I tried with SERVER=\\xxx.xxx.x.xxx, but it did not work.)

I installed ODBC driver with MDAC (Local/Client Component) on my machine, not File Server driver. This is the correct one, right?

Thank you
 
I'd like to add that I installed an evaluation version of ProvideX ODBC Driver version 4.21.1000 with MDAC (Local/Client Component).
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top