Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 VB remote connection to Sql Server

Author  Topic 

ThanosM
Starting Member

2 Posts

Posted - 2006-06-22 : 13:39:05
I have developed a database application using Visual Basic 6 and Sql Server 2000, and now i want it to connect to Sql Server that resides on another machine! How do i do this? I want to have Sql Server installed on a central machine, and i want my VB application to be able to connect to that Sql Server using OLEDB!! Or do i only do it using ODBC?? Thanx for all the help!!

timmy
Master Smack Fu Yak Hacker

1242 Posts

Posted - 2006-06-22 : 19:20:13
You should be able to do it using both.

I'm assuming you have a DSN setup on your machine (via ODBC Connection manager) to point to your local database. All you need to do is point it to the remote database. Suggest you do some reading up on DSN's.

Tim
Go to Top of Page

ThanosM
Starting Member

2 Posts

Posted - 2006-06-23 : 03:00:27
Well, i'm actually more interested in using OLEDB, because right now it connects to the local database through OLEDB! And i want it to connect to the remote DB through OLEDB! Another question that i have is, if each client machine should be running the client tools of Sql Server, or can i just have one Sql Server installation on the server machine? And i'm also asking this, because a newer version of this application that i'm developing, i'm making use of the SQL-DMO object! And i want all client machines to have access to this object! Thanx a lot for your help in advance!!!

Thanos
Go to Top of Page

timmy
Master Smack Fu Yak Hacker

1242 Posts

Posted - 2006-06-23 : 06:57:04
No - you don't need to install SQL Server client tools on all machines. Most machines should have MDAC (Microsoft Data Access Components IIRC) which contain all the OLEDB/ODBC stuff you should need.
And SQL-DMO should probably be included in whatever installation package you're creating. Your installation/packaging software should take care of this.
Go to Top of Page
   

- Advertisement -