David -- Ignoring, for the moment, the raging battle between the purists and practicalists as to what distinguishes a "real" database :-) , there are at least three ways I can think of to solve your problem:
(1) Buy a Linux ODBC driver for Access. I don't know if such a beast exists; maybe Merant has one. (2) There's a product (sorry, can't remember who makes it or what it costs) for Linux called an ODBC bridge that will let you set up an ODBC datasource on your Linux box that talks to an ODBC datasource on a Windows box. So you could install the bridge on your Linux host, then on the Windows machine define an ODBC datasource pointing to the Access database, then on the Linux machine define an ODBC datasource pointing through the bridge to the datasource you just defined on the Windows machine. (3) If you have a SQL Server 2000 available somewhere (SQL Server 7 may even be able to do this, I can't remember), then your problem may be solvable without having to purchase any additional third-party products. On the SQL Server, use Enterprise Manager or the appropriate SQL commands to define a Linked Server pointing to the Access database in one of two ways: either using the OLE DB Provider for Jet databases (Access, dBase, FoxPro, etc.), or using the OLE DB Provider for ODBC Datasources (which of course would also require that you establish an ODBC datasource on that SQL Server machine that points to the Access database). Once you have this Linked Server set up, you can use CF Linux's (either Pro or Enterprise) SQL Server ODBC driver to set up an ODBC datasource to the SQL Server. Then, through that datasource, using the appropriate four-part SQL syntax for references to tables addressed through Linked Server definitions, you can write cfqueries on your Linux machine that CF will pass to Linux ODBC, which will pass to the SQL Server, which will pass to Access. Sounds (and, admittedly, is) positively Rube Goldbergish, but when your budget for additional software purchases is zero and you happen to have a SQL Server 2000 lying around, I can say from experience that it definitely works. Note also that because the Windows ODBC driver for Jet databases will let you define a datasource pointing at any machine on the network (be sure to use UNC naming conventions in specifying the filename of the Access database; do not use a mapped drive letter), the Access database doesn't even necessarily have to reside on the same machine as the SQL Server. -- LBA David Siew wrote: > Hi all, > > Sorry. I havent got experience with CF on Linux. > > Is there anyway that I can set up a MS Access database as a datasource > on a Linux server installed with CFMX? Any advise is much appreciated. > > Thank you and regards > David > > ______________________________________________________________________ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
