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 FileMaker

I've developed a number of databases in FileMaker for a client, and am now in the process of converting them over to SQL Server. During the transition, there will be duplicates of tables in both platforms, so I must design a method of data synchronization, so that data maintenance need only be done in one database, not both. I've done it with DTS, but that's certainly not the most efficient. Instead, I'm trying to implement Linked Servers within SQL Server so that data can be updated dynamically with SQL statements. Has anyone ever had the pleasure of trying to do this? If so, would you mind sharing with me how you completed the Linked Server dialogue box (see attached) to connect to FileMaker.What is filemaker, and is it ODBC Compliant?

Does it have a system catalog?|||I have found the answer. In case you ever have to connect to FileMaker via a Linked Server, here's what you need:

1. The FileMaker file(s) must be opened, and set to Multi-User status and configured to have the Remote Data Access Companion enabled.
2. Set up a System DSN for the FileMaker Pro ODBC driver.
3. In the General tab of the ODBC FileMaker Pro Driver setup, ensure that the "Use Remote Connection" checkbox is checked, and the Server Address field is completed correctly (with either the IP address or the host name).
4. The Linked Server Properties dialog box needs only two entries: Provider Name to be "Microsoft OLE DB Provider for ODBC Drivers" (from the drop-down list), and Data Source to be your FileMaker System DSN as per item 2 above.

It was item 3 above that was causing all my problems. I was running FileMaker on the same (local) machine, and didn't think it would be considered a remote connection.

...Dave Ryan