Access Driver for CFMX on Linux

[skooch]

I am running CFMX 6.1 on RedHat Linux AS. I have an MS Access database on a
Windows server I want to access. CFMX does not come with a built-in Access ODBC
or JDBC driver. Is there any way to get this to work? I can not convert the
Access DB to MySQL as it is still used in Access.

Thanks.

[Stephanie]

You may want to do a search from the following link for MS Access Drivers and
see if any of the results suit your needs:

[url]http://developers.sun.com/product/jdbc/drivers[/url]

I hope this helps,

Stephanie Juma
Macromedia, Inc.

[skooch]

The results this link turns up are either outdated or not compatible with
Linux. I have an Access database which is currently modified on Windows using
Access forms so I can't convert it. I need to get the data into MySQL on a
regular basis and do not want to have to export and import the data. If
necessary I could probably set up an intermediary Windows server running CF.
Would this help?

[Stephanie]

If you install ColdFusion MX on Windows then you will have the option to run
the ODBC Driver for Access since you will have the the ODBC Socket Services
installed.

I hope this helps,

Stephanie Juma
Macromedia, Inc.

[OldCFer]

I think the only way to connect to MS Access is via a windows box because it's
a file based
DB and doesn't listen on a port so the MS Jet engine still comes into play.
What you could
do is duplicate the Access tables in MySql, link them into the Access DB, then
the Access
forms will use the MySql tables just like Access tables. That's what I did
but it was with
MS SQL.

[skooch]

That is a very interesting idea and that just might work. Can Access forms do
this to remote ODBC connections or does the MySQL DB need to be on the same
machine? If it will work through ODBC you have made my week!

[OldCFer]

Nope, your MYSQL DB can be anywhere. Just make sure you have the latest MYSQL
ODBC Drivers on your Access machine and set up the DSN via the Control panel
ODBC Data Sources. Then in Access go to File/Get External Data/link tables.
The
type of file is ODBC Data sources. Then choose the datasource you set up for
the
MYSQL datasource. You should be able to see all of the MYSQL tables. Choose
the tables you want. The Access forms can use them just like they were Access
tables.
If they are the same name and data types Access forms can't tell the
difference.

[ken_north@compuserve.com]

OldCFer wrote:

>> I think the only way to connect to MS Access is via a windows box

because it's
a file based DB and doesn't listen on a port so the MS Jet engine still
comes into play.

Depending on what API you want to use (JDBC or ODBC), there are several
alternatives.

Several companies make middleware servers that enable you to use a
single driver (JDBC or ODBC) to connect to the middleware server. The
middleware server uses ODBC, JDBC and/or native APIs to connect to the
data source. For example (where client refers to a database client):

Client -- JDBC --> Middleware ---- ODBC --> data source
Server

Catalog of 200+ ODBC drivers (and ODBC middleware servers):
[url]http://www.SQLSummit.com/ODBCVend.htm[/url]

Catalog of 120+ JDBC drivers (and JDBC middleware servers):
[url]http://www.SQLSummit.com/JDBCVend.htm[/url]

Catalog of 30+ .NET data providers:
[url]http://www.SQLSummit.com/DataProv.htm[/url]

Catalog of OLE DB Providers:
[url]http://www.SQLSummit.com/oledbVen.htm[/url]

Catalog of DB2 Extenders:
[url]http://www.SQLSummit.com/Extenven.htm[/url]

Catalog of XQuery Engines/Processors:
[url]http://www.SQLSummit.com/XQueryProv.htm[/url]

[ken_north@compuserve.com]

OldCFer wrote:

>> I think the only way to connect to MS Access is via a windows box

because it's
a file based DB and doesn't listen on a port so the MS Jet engine still
comes into play.

Depending on what API you want to use (JDBC or ODBC), there are several
alternatives.

Several companies make middleware servers that enable you to use a
single driver (JDBC or ODBC) to connect to the middleware server. The
middleware server uses ODBC, JDBC and/or native APIs to connect to the
data source. For example (where client refers to a database client):

Client -- JDBC --> Middleware ---- ODBC --> data source
Server

Catalog of 200+ ODBC drivers (and ODBC middleware servers):
[url]http://www.SQLSummit.com/ODBCVend.htm[/url]

Catalog of 120+ JDBC drivers (and JDBC middleware servers):
[url]http://www.SQLSummit.com/JDBCVend.htm[/url]

Catalog of 30+ .NET data providers:
[url]http://www.SQLSummit.com/DataProv.htm[/url]

Catalog of OLE DB Providers:
[url]http://www.SQLSummit.com/oledbVen.htm[/url]

Catalog of DB2 Extenders:
[url]http://www.SQLSummit.com/Extenven.htm[/url]

Catalog of XQuery Engines/Processors:
[url]http://www.SQLSummit.com/XQueryProv.htm[/url]