[Microsoft Access Driver (* Mdb * Accdb) For Windows 7 64 Bit
Iberio Ralda
I have been using Julia casually for a few months now, I am not a trained programmer in any form.
I am completely stumped on getting the ODBC package working to connect to a single access DB(.accdb) file.
Sorry to revive this old thread, but I also struggle to get data from Access to Julia.
The method described above does not work anymore because ODBC.DSN does not exist anymore in the current version of ODBC.jl.
This (unregistered) package can be used to test, or for inspiration on how to set up with the UCanAccess driver: GitHub - hellemo/Access.jl: Julia support for MS Access database files via JDBC and UCanAccess
Looks great, thanks!
I am not restricted to use ODBC, any way to get data from Access diretctly to Julia is fine for me.
I encounter an error when building and created an Issue for it, it would be great if you could take a look.
I've just installed ColdFusion 2021 as a Development server. I'm trying to attach an Access database as a Datasource. It comes back with something like "ODBC service not running, or is not installed." When I was installing CF2021, the ODBC Services checkbox on the sub-components installation page is greyed-out, so I am unable to check it. What next?
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).
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.
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".
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.
My experience is probably similar to yours. I made, and still make, Access databases for all sorts of things. And I used it for my public web sites for many years, as well. A while back, I started having issues with the server from time to time. My host supported me as best they could, but they finally told me that I was never going to have reliable use of an Access database with my site.
They suggested MySQL, and I went with it. After I went through the trouble of figuring out the connections & how to use the provided app, phpMyAdmin, I came to love it. You can create ODBC connections between your local site and your DB on the remote server, and it will work swimmingly.
I am trying to migrate from Access to MySQL, but Coldfusion keeps saying it cannot work with teh Community version of MySQL. I can't afford the Entriprise or Commercial versions. Is there a way around that?
There should be a free MySQL driver already installed, that will work with the MySQL Community database. If not, download the free MySQL JDBC driver and select "Other" as the datasource type. The CF docs cover how to do that, in detail.
However if, for whatever reason, you insisted on using MS Access on CF2021, then I would suggest you do so with JDBC instead of ODBC. You could then use the Open Source JDBC driver, UCanAccess; I did a post on it some years ago.
Great point, BKBK, about the options of available JDBC drivers. I keep forgetting to think of those (for those who desparately feel they need to stick with Access), but I should have recomended that or the other (that I seem to recall having seen).
Glad you offered that...along the the reminder to seriously reconsider getting off Access. The JDBC driver certainly helps resolve the ODBC issues, but it doesn't really address how Access is just not really designed for the volume of multi-user access that a web app/web server can throw it--though again I realize some will say "it was never a problem for all our years of using it".
Hello (I use google translator),
I finally got Lucee running on a Windows Server 2019 with IIS.
Now I would like to access Access databases (mdb) with Lucee.
Are there instructions for this?
Do I really need ucanaccess?
How do I install ucanaccess?
I downloaded it but there is no setup file, what next?
My personal advice is migrate that DB to another one (e.g. mariaDB or mySQL) in first place. There are lots of tools around and docs that makes that pretty easy. Probably easier than trying to make a data source connection to a modern web app engine like Lucee work.
I use Access as DB for more than 20 years, it works fine for small sites,
and it is very simple and flexible.
I just cut and paste my MDB file, and do what ever I want with the MDB on local.
In Lucee , you use ODBC driver : Update datasource connection Other - JDBC Driver (deprecated)
I work on Linux, but before I worked on windows.
Set Class and connection string in the declared datasource.
It is good to me to know other users with Ucanaccess driver.
mdb_file742434 59.1 KB
1, You are better off converting your access DB to MS sql express, which will import all your data into the tables / databases and have far better performance than access plus lucee supports MSSQL
2. You will need to install the ODBC drivers for your windows version, and you will need to install microsoft office Unable to use the Access ODBC, OLEDB or DAO interfaces outside Office Click-to-Run applications - Office Microsoft Learn
3. Lastly, you can follow this tutorial if you cant JUST LIVE without access, it is the JAVA connector how to, which you will have to wrap cfcode around
Java JDBC Example Connect to Microsoft Access Database
Ok, it took about 30min to try this, and I was able to make an access database work with an Lucee Express Version 5.3.10.97 on my Windows 10 Lap. You need to translate that to your installed server. But this works!!! If you have populated your Lucee installation with some other files, please restart from scratch. Here is a solution and the steps you need to make:
At Docker we are seeing a cavalcade of customers finding value in containers not just for greenfield microservice applications, but also as a key to modernizing legacy applications. One recent conversation involved a question: can a legacy line of business application that uses an Access database be transitioned to a container? Having not touched an Access database in many years, I set out to find an answer.
Needing a sample database that would be representative of an older application, I fired up Access 2017 and created a new database from the Northwind Traders template. This sample database started up as a .accdb file, the file format that Access moved to back in 2007. I wanted to lean more oldschool, so attempted an export to the older .mdb format. Unfortunately, Access refused the operation, citing the new features in-use that were not backwards compatible to previous formats.
With Northwind appearing to be a dead end, I looked online for a second sample database known to SQL aficionados as AdventureWorks. Codeplex had a copy, and although it downloaded as a .aacdb, Access easily exported it as a .mdb by using the Access 2000 Database option.
With a database secured, it was time to stand up a web application to interface with the data. My goal was to create a proof of concept web application that communicate with the database and displays data via a browser.
Once the solution provisioned, I created a default.aspx web form and an App_Data folder. The AdventureWorks.mdb file went into App_Data, and I scaffolded out a simple page in the aspx file by importing the Bootstrap library and adding a heading.
Creating a container involves crafting a Dockerfile. As a base image, microsoft/windowsservernano is a lighter weight base, however legacy applications rely on a myriad of features and capabilities that are simply not possible in nano. For this app, I instead turned to microsoft/aspnet:4.6.2, based on the larger and more robust Windows Server Core.
795a8134c1