Now that my issue is solved, I thought I would come back and put a bow on this one in case somebody else finds themselves in the same position.
In a nutshell, I was unable to locate a 64 bit ODBC driver for Access. I may have seen a reference to installing the latest, 64 bit version of Access to get the driver, but I'm not sure I read that right. And even if it's true, I'm not about to purchase a major office app and install it on my server to get a db driver. So my issue came down to converting the Access db's to MySQL. I had only 6-8 databases to convert. If you have dozens or more, this solution may not be what you need. I'm happy to be free of the Access db's, but I'm not very happy that I had to resort to this. These are very old, lightly used sites that would have likely died a natural death or eventually been replaced with something newer/better, without this work ever having been done, if I had been able to locate a driver. This conversion was wasted time. (And another glaring lesson about avoiding proprietary everything) After some quick research on tools to help with the conversion, I ended up spending a mere $39 on a small program called Access to MySQL 5.5, from a company called Intelligent Converters at http://www.convert-in.com/. I am very pleased with the product. It allowed me the option of dumping the conversions to sql dump files. I like that. It means I don't have another 3rd party program messing directly with my db server, and allows editing the files if needed before importing them. I still ended up doing some work by hand. I doubt that is completely avoidable. First, this is going from an environment where table/view names are not case-sensitive to one that is. Do yourself a favor and open your Access db's first and get the case-sensitivity right on all the table and query names ... including opening the sql view of all your queries (views) to ensure they are written with the correct case on table and query names. (then you get to address the same issue in your code) (and yes, I hear all you Linux guys choking on your laughter as you read this!) As could have probably been predicted, I had some trouble wherever I had Date/Time functions in my SQL. I had some trouble with views that referenced other views that had not yet been created. Probably best to plan on doing a few test runs... watch the logs and fix the glitches as they arise. I've probably not given enough kudos to the conversion software. I didn't use all of the available options. You can download a trial version first to get a feel for how it would work for you. So there you have it. Glad it's done, but wish it hadn't been necessary. tx, c -- online documentation: http://openbd.org/manual/ http://groups.google.com/group/openbd?hl=en
