I have a Delphi 10 programme which reads an Access database (.mdb). I believe it does this through DAO. I was using Access 2016 and this worked fine. I have now upgraded to Access 2019 and it crashes (specifically, in the DAO_TLB unit it errors saying, "Project raised exception class EOleSysError with message 'Class not registered'.")
I am not sure what information I should include here that would be useful - please let me know.
Related
I have here a specific application I am forced to use. This application uses Access as data storage.
This application is older and was once developed for Office 2013. Our company computers have now Office 2016 installed, with Access 2016.
After the installation of Access 2016 this application stopped running. It hangs immediately after start.
So i installed Access Runtime 2013 and application first worked fine. But as soon as I open Access 2016, there is a repair run installing something in the background and application again stopps working. After executing Repair on Access Runtime 2013, it works again until Access 2016 ist again opened.
After checking the dump of this Application I see that after running repair of Access 2013, Office15-DLLs are used. After starting Access 2016 and repair run, Office16-DLLs are linked and application stops working.
All those repair runs take minutes, so they are very annoying, as I often have to switch between both applications.
Is there any other / better way to handle it? I tried to set Runtime 2013 into the PATH of my application, no changes. Can I somehow force the application to use Runtime 2013 instead of Access 2016?
Thanks!
I've made an application on an MS Access 2016 with 365 subscription and deployed an .accde file. When I try to open that file on another PC with runtime installed (tried with 2016 4288-1001 64bit and 2013 64bit) I get an error saying "Database you are trying to open requires a newer version of Microsoft Access".
I know that are some issues related to runtime and 365, but some people said that using runtime 2013 solved their problem (but not mine).
Anyone have a solution for this?
The problem was that some of my table fields data was set as "Large Number".
I don't know why, but Access Runtime 2016 can't read this data type, changing the fields to "Number" made the deployed ".accde" open normally.
Source: https://support.microsoft.com/en-us/help/3208802/-database-you-are-trying-to-open-requires-a-newer-version-of-microsoft
I tried connecting to MS Access 2016 database using OLEDB 12 and it worked. However after a few connections(sequential), I noticed that my code got stuck while opening the connection. It would neither fail or exit, just stuck.
I have that that I am properly closing the connection after use.
When I installed Access 2013 runtime and used OLEDB 15, the issue was solved.
But I am unable to install this runtime on all my nodes in production.
Is there some known issue on using OLEDB 12 to connect to Access 2016. Is it solvable by some code fix ir will I have to move to Access 2013 runtime.
I am writing a VB6 program that needs to open an MS Access 2010 database (.mdb) but I get an "invalid file type" error when I try. Do I need to get updated driver(s)?
The answer I needed but did not know it was "install VB6 SP6". I had installed VB6 on a new PC a couple of years ago, and was not aware of the service pack to let VB6 handle post MS Access 1997 tables. But thanks anyway.
I have an Access database in source control on TFS that I need to pull down onto another machine (XP, Office 2007). I have the Team Foundation Server MSSCCI Provider 2010 installed and I can successfully see the source. However, when I try to have it created it fails, giving me this error:
Failed to create a new database on a Team Foundation project.
Any idea what I've done wrong on this machine?
I think the solution to this was that I had sent the database up to TFS from Access 2010, but was trying to pull it down to another machine with Access 2010. I thought the two versions shouldn't matter, but sending it up to TFS in Access 2007 and bringing it down in Access 2007 and Access 2010 appeared to work.