Moriarty, the first thing that needs to be said ("what next?") is that in the year 2021, it really is time to get off of Access as a db used for any web app server like cf (and yes, even if used by only one person, let alone many).
I know that will upset some. And others may disagree, perhaps vehemently. Let me elaborate.
First, yes, CF has long supported it, but it no longer does formally, at least according to the cf2021 support matrix:
https://helpx.adobe.com/pdf/coldfusion2021-support-matrix.pdf
And this is not new in cf2021. The last support matrix to list it was in fact cf11, from 2014.
But yes, the cf admin still lists it as a db type, as you are seeing. (I almost wonder if that's a mistake, though you will even find some comments from Adobe folks since 2014 trying to help with workarounds.)
And yes, there is indeed still the cf odbc service. (As you say it's greyed out in the 2021 gui installer. That said, I find it's still being enabled as a service on windows, regardless, which was a surprise.) BTW, that's not there JUST for Access but for any use of odbc--which really also ought to be strongly discouraged these days.
And use of odbc itself is hardly needed any more: to be clear, all other db's that cf supports (and offers drivers for) are instead JDBC drivers. These have been the main db types since cf6 in 2001. But there are some very old integrations that still support only odbc--and even those are a challenge to keep working in recent cf releases.
Indeed, people have been trying to "keep access to Access" in CF in recent releases. You will find on the web (and may hear here) various discussions of workarounds trying to get it/keep it going.
All are like bailing water on a sinking ship. Get out of the boat. Switch to any alternative that cf DOES support. And note that there are free implementations of sql server, mysql, oracle, postgres, and more. And yes, I mean free for production use.
Yes, converting the db can be (or seem like it would be) a hassle, but there are tools to help, especially between Access and sql server. And no, there may be zero need of any code or sql changes, so the conversion effort really could take just minutes or hours, though of course testing is needed. Such a conversion should not be a crazy long effort, though one would understandably fear that.
(And yes, this move would disrupt people who have long done things like upload a new mdb to the server from their own machine or a local network. Again, that was never a great idea even 20 years ago, though people had their justifications. There are ways to do the same upload/sync process with a db in sql server, etc. They're just different steps. And they're nearly always better in many ways.)
I know all this is not what people using Access want to hear, especially if this is in the critical path of moving to a new cf version. They may even demand of Adobe that this "must be made to work".
And again some may toss you supplies to keep the boat afloat. I can no longer in good conscience try to help people plug those holes.
The boat is sinking. Really, get off of it. But I'm referring only to use of Access with CF, of course. The *cf boat" is awesome, upright, and especially in cf2021 fitted with modern features and conveniences to carry its passengers and crew forward, despite the sneers from folks in other boats, or even those wanting to debark cf at their next chance.
/Charlie (troubleshooter, carehart.org)
7
Replies
AdChoices