Linked Server to IBM AS400

I need to create a linked server to communicate with an AS400 server by using
Client Access ODBC and then launch some query on particular files (inside
libraries).
How can I solve this issue?
I haven't founded any documentation about this subject.
Many thanks for your suggestsInstall Client Access on the SQL Server box and make sure
you have the client updated with whatever service pack level
based on updates to your AS400. Then configure the linked
server as described in books online under Linked Servers,
configuring.
For data source, use the IP address of the AS400.
For provider string, you need to include the library you are
using, connect timeout setting and code page. There is some
documentation for the settings in the Client Access help
files.
You'd set the provider string somewhat like:
InitCat=YourLibrary;CCSID=37;PCCodePage=1252;
Data Source=xxx.xxx.xxx.xxx
Settings will depend on how your AS400 is configured. Again,
the Client Access help files have information on the
necessary connection string settings.
-Sue
On Thu, 6 Jul 2006 06:56:01 -0700, Pasquale
<Pasquale@.discussions.microsoft.com> wrote:
>I need to create a linked server to communicate with an AS400 server by using
>Client Access ODBC and then launch some query on particular files (inside
>libraries).
>How can I solve this issue?
>I haven't founded any documentation about this subject.
>Many thanks for your suggests|||Oh thanks!
I have tried to create a Client Access ODBC link, then I create a linked
server by setting only the data source with the Client Access ODBC data
source and user id + pwd. Then I have executed a SELECT by indicating the
linkedserver.linkedserver.libraryname.filename and I have the correct results.
Many thanks
"Sue Hoegemeier" wrote:
> Install Client Access on the SQL Server box and make sure
> you have the client updated with whatever service pack level
> based on updates to your AS400. Then configure the linked
> server as described in books online under Linked Servers,
> configuring.
> For data source, use the IP address of the AS400.
> For provider string, you need to include the library you are
> using, connect timeout setting and code page. There is some
> documentation for the settings in the Client Access help
> files.
> You'd set the provider string somewhat like:
> InitCat=YourLibrary;CCSID=37;PCCodePage=1252;
> Data Source=xxx.xxx.xxx.xxx
> Settings will depend on how your AS400 is configured. Again,
> the Client Access help files have information on the
> necessary connection string settings.
> -Sue
> On Thu, 6 Jul 2006 06:56:01 -0700, Pasquale
> <Pasquale@.discussions.microsoft.com> wrote:
> >I need to create a linked server to communicate with an AS400 server by using
> >Client Access ODBC and then launch some query on particular files (inside
> >libraries).
> >How can I solve this issue?
> >I haven't founded any documentation about this subject.
> >
> >Many thanks for your suggests
>

Linked Server to IBM AS400

I need to create a linked server to communicate with an AS400 server by usin
g
Client Access ODBC and then launch some query on particular files (inside
libraries).
How can I solve this issue?
I haven't founded any documentation about this subject.
Many thanks for your suggestsInstall Client Access on the SQL Server box and make sure
you have the client updated with whatever service pack level
based on updates to your AS400. Then configure the linked
server as described in books online under Linked Servers,
configuring.
For data source, use the IP address of the AS400.
For provider string, you need to include the library you are
using, connect timeout setting and code page. There is some
documentation for the settings in the Client Access help
files.
You'd set the provider string somewhat like:
InitCat=YourLibrary;CCSID=37;PCCodePage=
1252;
Data Source=xxx.xxx.xxx.xxx
Settings will depend on how your AS400 is configured. Again,
the Client Access help files have information on the
necessary connection string settings.
-Sue
On Thu, 6 Jul 2006 06:56:01 -0700, Pasquale
<Pasquale@.discussions.microsoft.com> wrote:

>I need to create a linked server to communicate with an AS400 server by usi
ng
>Client Access ODBC and then launch some query on particular files (inside
>libraries).
>How can I solve this issue?
>I haven't founded any documentation about this subject.
>Many thanks for your suggests|||Oh thanks!
I have tried to create a Client Access ODBC link, then I create a linked
server by setting only the data source with the Client Access ODBC data
source and user id + pwd. Then I have executed a SELECT by indicating the
linkedserver.linkedserver.libraryname.filename and I have the correct result
s.
Many thanks
"Sue Hoegemeier" wrote:

> Install Client Access on the SQL Server box and make sure
> you have the client updated with whatever service pack level
> based on updates to your AS400. Then configure the linked
> server as described in books online under Linked Servers,
> configuring.
> For data source, use the IP address of the AS400.
> For provider string, you need to include the library you are
> using, connect timeout setting and code page. There is some
> documentation for the settings in the Client Access help
> files.
> You'd set the provider string somewhat like:
> InitCat=YourLibrary;CCSID=37;PCCodePage=
1252;
> Data Source=xxx.xxx.xxx.xxx
> Settings will depend on how your AS400 is configured. Again,
> the Client Access help files have information on the
> necessary connection string settings.
> -Sue
> On Thu, 6 Jul 2006 06:56:01 -0700, Pasquale
> <Pasquale@.discussions.microsoft.com> wrote:
>
>

linked server to Excel

We've created a linked server to access an Excel spreadsheet that resides on
the same server as SQL Server 2000. If we log on to the database server
(Windows 2000), then launch Enterprise Manager, the linked server works
perfectly.
But, if we launch Enterprise Manager from a desktop machine (Windows 2000)
and attempt to use the linked server we get: "Error 7399 : OLE DB provider
'Microsoft.Jet.OLEDB.4.0' reported an error."
Any ideas?SELECT *
FROM OpenDataSource( 'Microsoft.Jet.OLEDB.4.0',
'Data Source="c:\test.xls";User ID=;Password=;Extended properties=Excel
5.0')...[test1$]
And the 'test1' is the name of work sheet.
"Vince" wrote:

> We've created a linked server to access an Excel spreadsheet that resides
on
> the same server as SQL Server 2000. If we log on to the database server
> (Windows 2000), then launch Enterprise Manager, the linked server works
> perfectly.
> But, if we launch Enterprise Manager from a desktop machine (Windows 2000)
> and attempt to use the linked server we get: "Error 7399 : OLE DB provide
r
> 'Microsoft.Jet.OLEDB.4.0' reported an error."
> Any ideas?
>
>|||Thanx for the response.
However, I get the same result.
"luyan" <luyan@.discussions.microsoft.com> wrote in message
news:FFE5CD8B-ED99-4568-8B55-21AB6A73242C@.microsoft.com...[vbcol=seagreen]
> SELECT *
> FROM OpenDataSource( 'Microsoft.Jet.OLEDB.4.0',
> 'Data Source="c:\test.xls";User ID=;Password=;Extended properties=Excel
> 5.0')...[test1$]
> And the 'test1' is the name of work sheet.
> "Vince" wrote:
>
resides on[vbcol=seagreen]
2000)[vbcol=seagreen]
provider[vbcol=seagreen]

linked server to Excel

We've created a linked server to access an Excel spreadsheet that resides on
the same server as SQL Server 2000. If we log on to the database server
(Windows 2000), then launch Enterprise Manager, the linked server works
perfectly.
But, if we launch Enterprise Manager from a desktop machine (Windows 2000)
and attempt to use the linked server we get: "Error 7399 : OLE DB provider
'Microsoft.Jet.OLEDB.4.0' reported an error."
Any ideas?
SELECT *
FROM OpenDataSource( 'Microsoft.Jet.OLEDB.4.0',
'Data Source="c:\test.xls";User ID=;Password=;Extended properties=Excel
5.0')...[test1$]
And the 'test1' is the name of work sheet.
"Vince" wrote:

> We've created a linked server to access an Excel spreadsheet that resides on
> the same server as SQL Server 2000. If we log on to the database server
> (Windows 2000), then launch Enterprise Manager, the linked server works
> perfectly.
> But, if we launch Enterprise Manager from a desktop machine (Windows 2000)
> and attempt to use the linked server we get: "Error 7399 : OLE DB provider
> 'Microsoft.Jet.OLEDB.4.0' reported an error."
> Any ideas?
>
>
|||Thanx for the response.
However, I get the same result.
"luyan" <luyan@.discussions.microsoft.com> wrote in message
news:FFE5CD8B-ED99-4568-8B55-21AB6A73242C@.microsoft.com...[vbcol=seagreen]
> SELECT *
> FROM OpenDataSource( 'Microsoft.Jet.OLEDB.4.0',
> 'Data Source="c:\test.xls";User ID=;Password=;Extended properties=Excel
> 5.0')...[test1$]
> And the 'test1' is the name of work sheet.
> "Vince" wrote:
resides on[vbcol=seagreen]
2000)[vbcol=seagreen]
provider[vbcol=seagreen]

linked server to Excel

We've created a linked server to access an Excel spreadsheet that resides on
the same server as SQL Server 2000. If we log on to the database server
(Windows 2000), then launch Enterprise Manager, the linked server works
perfectly.
But, if we launch Enterprise Manager from a desktop machine (Windows 2000)
and attempt to use the linked server we get: "Error 7399 : OLE DB provider
'Microsoft.Jet.OLEDB.4.0' reported an error."
Any ideas?SELECT *
FROM OpenDataSource( 'Microsoft.Jet.OLEDB.4.0',
'Data Source="c:\test.xls";User ID=;Password=;Extended properties=Excel
5.0')...[test1$]
And the 'test1' is the name of work sheet.
"Vince" wrote:
> We've created a linked server to access an Excel spreadsheet that resides on
> the same server as SQL Server 2000. If we log on to the database server
> (Windows 2000), then launch Enterprise Manager, the linked server works
> perfectly.
> But, if we launch Enterprise Manager from a desktop machine (Windows 2000)
> and attempt to use the linked server we get: "Error 7399 : OLE DB provider
> 'Microsoft.Jet.OLEDB.4.0' reported an error."
> Any ideas?
>
>|||Thanx for the response.
However, I get the same result.
"luyan" <luyan@.discussions.microsoft.com> wrote in message
news:FFE5CD8B-ED99-4568-8B55-21AB6A73242C@.microsoft.com...
> SELECT *
> FROM OpenDataSource( 'Microsoft.Jet.OLEDB.4.0',
> 'Data Source="c:\test.xls";User ID=;Password=;Extended properties=Excel
> 5.0')...[test1$]
> And the 'test1' is the name of work sheet.
> "Vince" wrote:
> > We've created a linked server to access an Excel spreadsheet that
resides on
> > the same server as SQL Server 2000. If we log on to the database server
> > (Windows 2000), then launch Enterprise Manager, the linked server works
> > perfectly.
> >
> > But, if we launch Enterprise Manager from a desktop machine (Windows
2000)
> > and attempt to use the linked server we get: "Error 7399 : OLE DB
provider
> > 'Microsoft.Jet.OLEDB.4.0' reported an error."
> >
> > Any ideas?
> >
> >
> >