Setting up ODBC Data Source with FileMaker

[andrej27]

I'm trying to establish an ODBC Data Source in Windows 98 and have been unsuccessful. I can add a FileMaker Pro driver to the ODBC Data Source list, but I don't get an option to select the database that will utilize the source when I add the Data Source. When I add an Access driver to the ODBC Data Source list, I get an option to select a database.

I am using the FileMaker Pro 5.5 demo. I'm trying FileMaker before deciding whether or not it will work with what I'm doing.

I am using FileMaker in a way that's probably unusual to most FileMaker developers. I'm using a FileMaker database as a content holder for a multimedia project that I'm creating with Macromedia Authorware. There is an Xtra (plug-in) for Macromedia Authorware that allows Authorware to connect to any ODBC compliant database. But, it needs the ODBC Data Source to point to the database for it.

Is there any way to do this with FileMaker Pro?

Thanks for any help you can give me. I'm really at my wits end with finding a solution for this. If you have specific questions, please contact me at [email protected] or 717-561-0976.

Thanks again.

[Anatoli]

I am doing that every day.

The database name can be selected later, when building query. At first it can be only selected named FM ODBC.

Later when the query is constructed e.g. in Excel via Microsoft Query, and then the database names can be specified.

But you'll be better of to do it through CDML and WebCompanion. Cheaper to develop and faster to serve. The ODBC way has not a single advantage.

[andrej27]

Are you doing it every day with Macromedia Authorware and the OpenDBC Xtra?

This is different than selecting from pull-down menus in Excel or Access. This is all happening behind the scenes in Authorware using the Xtra.

[Anatoli]

Andy,

not with Macromedia.

But I am getting data from FM every day through ODBC.

I can confirm, that FM and ODBC works, that is all.

Anatoli

[cowtram]

Having set up the DSN (which does not specify a DB) I can successfully run SQL Queries on a DB through an ASP script.

var oRS=Server.CreateObject("ADODB.recordset");

oRS.Open('SELECT * FROM myFMDB.fp5 WHERE fieldname="value"', "DSN=myDSN")

One thing I would say is that it seems important not to have more then one copy of the DB with the same name on the local machine/network.

This is because, since the DSN does not specify a DB, The connection source must be a unique DB Name.

So you just use the name of your DB in your connection source.

This is just my observation.

HTH