<div>
It sounds like the best option is to create a linked server. &nbsp;This would allow you to access data on the second server by using table names like [SRVR002].database.dbo.tab<wbr />le from the server you are connected to.<br />
<br />
Please see <a href="http://msdn.microsoft.com/en-gb/library/ff772782.aspx" rel="ugc">this Microsoft article</a> for detailed information.
</div>


<div>
I thought of that as well. &nbsp;And I believe it works well when you create the LINKS and then use that within the SQL Management's Query area.<br />
<br />
However, I want to do this directly from VB6.<br />
<br />
Is there a way to reference the LINKS within VB6?<br />
<br />
Thanks
</div>


<div>
You can set up a Linked Server on one of both MSSQLs. That allows the server the link is defined in to connect to the other one with something like<br />
<b> &nbsp; insert into [MySecondServer\instanceNa<wbr />me].DB2.Sc<wbr />hema.Tbl2 select * from DB1..Tbl1</b>
</div>


<div>
As soon as you have defined the Linked Server entry, you can use it in any SQL tool or programming language, including VB6.
</div>


<div>
makes sense, let me try this and I will let you know.
</div>


<div>
Qlemo,<br />
<br />
I first created the LINKED server and then tried the reference in my code and got INVALID OBJECT NAME.<br />
<br />
So just to make sure that I got the LINK correct. &nbsp;I went into the SQL Server Management and then created a simple SELECT on the &quot;linked&quot; tables and got the following:<br />
<br />
OLE DB provider &quot;SQLNCLI10&quot; for linked server &quot;SRV-NEWANA&quot; returned message &quot;Unspecified error&quot;.<br />
OLE DB provider &quot;SQLNCLI10&quot; for linked server &quot;SRV-NEWANA&quot; returned message &quot;The stored procedure required to complete this operation could not be found on the server. Please contact your system administrator.&quot;.<br />
Msg 7311, Level 16, State 2, Line 1<br />
Cannot obtain the schema rowset &quot;DBSCHEMA_TABLES_INFO&quot; for OLE DB provider &quot;SQLNCLI10&quot; for linked server &quot;SERVER1&quot;. The provider supports the interface, but returns a failure code when it is used.<br />
<br />
<br />
Any ideas?
</div>


<div>
No clue. You are, of course, trying to access MSSQL, do you?
</div>


<div>
Yes that is correct. &nbsp;One server is SQL 2000 and the other is SQL 2008 R2.
</div>


<div>
<div class="content wysiwyg-content">
I am currently using ADODB connections to make my queries from VB6 to SQL servers. &nbsp;My question is how do you make a statement that will reference 2 different SQL servers? &nbsp;I want to eventually query one SQL server, take data from a particular table and then INSERT that into a different SQL server.<br />
<br />
Below I have sample code that I use currently to transfer data from one table to another on the SAME SQL server.<br />
<br />
&nbsp; &nbsp; Set MyRec = CreateObject(&quot;adodb.record<wbr />set&quot;)<br />
&nbsp; &nbsp; MyConn.Open = &quot;provider=SQLOLEDB;Server=<wbr />testserver<wbr />;database=<wbr />Data1;user<wbr /> id=sa;password=test123&quot;<br />
&nbsp; &nbsp; sSQL = &quot;INSERT INTO [Data1].DBO.Table2_t &quot;<br />
&nbsp; &nbsp; sSQL = sSQL &amp;&nbsp;&quot;SELECT [Data1].DBO.Table1_t.* &quot;<br />
&nbsp; &nbsp; sSQL = sSQL &amp;&nbsp;&quot;FROM [Data1].DBO.Table1_t; &quot;<br />
&nbsp; &nbsp; MyConn.commandtimeout = 0<br />
&nbsp; &nbsp; MyRec.Open sSQL, MyConn<br />
&nbsp; &nbsp; MyConn.Close<br />
<br />
Thanks
</div>
</div>


I am currently using ADODB connections to make my queries from VB6 to SQL servers.  My question is how do you make a statement that will reference 2 different SQL servers?  I want to eventually query one SQL server, take data from a particular table and then INSERT that into a different SQL server.

Below I have sample code that I use currently to transfer data from one table to another on the SAME SQL server.

    Set MyRec = CreateObject("adodb.recordset")
    MyConn.Open = "provider=SQLOLEDB;Server=testserver;database=Data1;user id=sa;password=test123"
    sSQL = "INSERT INTO [Data1].DBO.Table2_t "
    sSQL = sSQL & "SELECT [Data1].DBO.Table1_t.* "
    sSQL = sSQL & "FROM [Data1].DBO.Table1_t; "
    MyConn.commandtimeout = 0
    MyRec.Open sSQL, MyConn
    MyConn.Close

Thanks

Using an ADODB connection to query 2 different servers

Visual Basic is Microsoft’s event-driven programming language and integrated development environment (IDE) for its Component Object Model (COM) programming model. It is relatively easy to learn and use because of its graphical development features and BASIC heritage. It has been replaced with VB.NET, and is very similar to VBA (Visual Basic for Applications), the programming language for the Microsoft Office product line.

Visual Basic Classic

VBScript (Visual Basic Scripting Edition) is an interpreted scripting language developed by Microsoft that is modeled on Visual Basic, but with some important differences. VBScript is commonly used for automating administrative and other tasks in Windows operating systems (by means of the Windows Script Host) and for server-side scripting in ASP web applications. It is also used for client-side scripting in Internet Explorer, specifically in intranet web applications.