Novice trying to use Microsoft Access 2010 Runtime

Topic

New Reply

Hope someone can help a novice on this…

I’m trying to read a Microsoft Access database (MDB file). I do not have Office installed (because my old Office/XP CD has data errors, and MSFT won’t replace CDs that old), so I’m trying Microsoft Access 2010 Runtime.

I am running Windows 10 Pro.

I downloaded Microsoft Access 2010 Runtime from the MSFT site (http://www.microsoft.com/en-us/download/details.aspx?id=10910 ), and ran the Setup. The message said “Installed Successfully”.

My question: Now what the heck do I do:rolleyes:? I tried clicking on a few of my MDB files but W10 then asks me which program it should use (Microsoft Access 2010 Runtime is not listed as a choice). How the heck can I read those files?

Any advice would sure be appreciated!

Thanks,

Alan

Reply | Quote

Replies

The runtime is to create a database for someone who hasn’t got Access to run, it won’t read a database first. You need a copy of Access to be bale to open your D/Bs. You will either have to purchase one, or ask someone with Access to read them for you. I don’t think that Base (from Libre Office or Open Office) will open them (but I can’t check this at the moment).

Others might know of ways to read Access databases without Access, but I’m afraid I don’t.

Right, just tried opening an Access db in LibreOffices Base (their database app). You have to ‘Connect to an existing database’ and select ‘Microsoft Access’ on the dropdown with JDBC in it. That will open your tables. I’ll check if forms et al work (VBA won’t).

Second edit – it looks like only tables are available, it won’t give you forms or queries.

Third edit – I suppose that I should have said that LibreOfficeis free.

Eliminate spare time: start programming PowerShell

Reply | Quote

The runtime is to create a database for someone who hasn’t got Access to run, it won’t read a database first.

That is not true.

The Access Runtime can only “read” database and “execute”. The Runtime version is the same bits as the full version with all the designers and navigation pane disabled.

The Access runtime is a “viewer” is similar to a PDF viewer if ofr PDF files. A PDF viewer can open the PDF and fill out forms but it can’t edit/desing it like the full version of Adobe Acrobat.

OK Rick, the description seemed (to me) to imply you needed Access to create runtimes for those who didn’t have Access but not that it would open databases. But experience trumps descriptions!

To open an Access database and view the forms and report you MUST have a version of Access.

There are two versions:

1) The full version which also has the ability to design (create/edit) forms, reports, queries,, modules,

2) The Runtime version. No designer capabilities. When opening a database with the Access Runtime you do not have the navigation pane (or database windows in 2003 and older). To use the Access Runtime to view a database it has to be configure properly. If there is not an autoexec macro to open a “startup” form or the startup form option has not been set you will get just a blank window.

I have been selling Access applications using the Access Runtime since it was first released for Access 97. There has been much confusion on what it is and how to use it. Prior to Avcess 2007 you have to purchase the Access Developer kit to get a license that gave you the rights to deploy the Access runtime. Starting with Access 2007 the Runtime and deployment tools became free. I never us the 2007 and later Package and Deployment Wizard. There really is not need. You can simply download the free Access runtime and install it. Copy you .accde or .accdb to the PC with the Access runtime and double click it. I prefer to create a shortcut to open it.

One of the issue with using the Acess 2007 an later rutime is the new security mode. The Access runtime does not have the ability to set eh trusted locations for the GUI. You have to set do it some other way.

This may help: What is the Access Runtime Version?

Reply | Quote

Hi Rick (and Geek and Coach),

Thank you again for all your time and help. I’m very fortunate to have found this site (I’ve been a Win Secrets subscriber for years.)

Good news to report (and I hope it might help someone in the future who sees this): I think I have gotten everything working (at least so far).

Here’s what I did:

1. I found an old RT Setup buried on my PC. It’s the RT2000 version (I assume that means it’s from 15 years ago). I recall it was distributed with an old version of the databases I’ve been struggling with.

2. I Removed the RT 2007 version that wouldn’t let me past the database opening screen before it gave me that indecipherable warning.

3. I then installed the old 2000 RT version and “pointed’ the “Open With” to the Access.exe it installed (in “C:Program Files (x86)Microsoft OfficeARTOfficeMSACCESS.EXE”

I then opened the first DB and it works just fine (including the Queries). I still need to try the other DBs (all from the same author), but I’m optimistic.

Thank you again Rick (and RetiredGeek and HiTechCoach). I’ve learned a lot and really appreciate it.

Alan

Reply | Quote

Hi Rick (and Geek and Coach),

Thank you again for all your time and help. I’m very fortunate to have found this site (I’ve been a Win Secrets subscriber for years.)

Good news to report (and I hope it might help someone in the future who sees this): I think I have gotten everything working (at least so far).

Here’s what I did:

1. I found an old RT Setup buried on my PC. It’s the RT2000 version (I assume that means it’s from 15 years ago). I recall it was distributed with an old version of the databases I’ve been struggling with.

2. I Removed the RT 2007 version that wouldn’t let me past the database opening screen before it gave me that indecipherable warning.

3. I then installed the old 2000 RT version and “pointed’ the “Open With” to the Access.exe it installed (in “C:Program Files (x86)Microsoft OfficeARTOfficeMSACCESS.EXE”

I then opened the first DB and it works just fine (including the Queries). I still need to try the other DBs (all from the same author), but I’m optimistic.

Thank you again Rick (and RetiredGeek and HiTechCoach). I’ve learned a lot and really appreciate it.

Alan

Alan,

Glad to here found a solution.

To use the Access 2007 or later runtime you have to create a trusted location for the database or set the macro security level to low by making a windows registry entry.

Reply | Quote

I tried clicking on a few of my MDB files but W10 then asks me which program it should use (Microsoft Access 2010 Runtime is not listed as a choice). How the heck can I read those files?

Hi Alan – That’s strange. I just downloaded the 32-bit runtime from the link you gave and installed it in Windows 10 Pro. When I clicked on an old Access 97 .MDB file the forms example came straight up no problem.

42393-access-runtime
Click to enlarge

Try again but this time, when W10 asks which program to use, browse to the MSACCESS.EXE file.

42392-access-runtime1
Click to enlarge

Have a look at What is the difference between Access and the Microsoft Access Runtime? for a brief description.

Hope this helps…

Reply | Quote

Thank you, Rick (and everyone). I appreciate you taking the time to help.

Clearly, I am doing something wrong.

When I installed the RT (and it said successfully) the Office folder it created contains only a DLL and one other non-EXE. I did Search for an “Access.exe” but did not succeed.

I even tried the Setup a second time and that time I chose “Repair”. Again it seemed to succeed, but alas, no Access.exe to be found.

(Did the RT package create that “Office 14” directory for you? I do not have a similar directory. I only have that Office directory that’s pretty much empty.)

I can’t imagine the 64-bit RT is different from the 32. In any event, I am still lost:(

Thanks again,

Alan

Hi Alan – That’s strange. I just downloaded the 32-bit runtime from the link you gave and installed it in Windows 10 Pro. When I clicked on an old Access 97 .MDB file the forms example came straight up no problem.

42393-access-runtime
Click to enlarge

Try again but this time, when W10 asks which program to use, browse to the MSACCESS.EXE file.

42392-access-runtime1
Click to enlarge

Have a look at What is the difference between Access and the Microsoft Access Runtime? for a brief description.

Hope this helps…

Reply | Quote

I can’t imagine the 64-bit RT is different from the 32. In any event, I am still lost:(
Alan

Alan,

The 64-bit version should be avoided. It is much different that the 32-bit. There are lots of compatibility issues and bugs.

I would only use the 32-bit version to open your older .mdb databases.

Also check out:

Known issues with Office and Windows 10

Reply | Quote

Rick, I don’t think the OP has Access installed, so your suggestion won’t work (or at least I don’t think it will)

Eliminate spare time: start programming PowerShell

Reply | Quote

Rick, I don’t think the OP has Access installed, so your suggestion won’t work (or at least I don’t think it will)

I don’t have Access installed either, just the runtime that the OP is referring to. The OP should be able to use pre-existing .MDBs (e.g. to enter data, use pre-existing forms, etc.) but won’t be able to edit, add or create additional functionality to the database structure itself.

This why Access developers distribute the runtime to end-users… so they can’t edit the database structure, only manipulate data, use forms and reports, etc. that the developer has created.

Reply | Quote

OK Rick, the description seemed (to me) to imply you needed Access to create runtimes for those who didn’t have Access but not that it would open databases. But experience trumps descriptions!

Eliminate spare time: start programming PowerShell

Reply | Quote

Hi Alan,

Yes, the run-time installer created the Office 14 folder and sub-folders.

Do you have an antivirus program running (other than Win 10’s built-in Defender)? If so, try temporarily disabling it and doing the install again – not Repair – from a fresh download, in case the installer has a problem.

Also, make sure you are using the 32-bit installer, not the 64-bit installer.

(This is advice from Microsoft: “We recommend the 32-bit version of Office for most users, because it’s more compatible with most other applications, especially third-party add-ins. This is why the 32-bit version of Office 2013 is installed by default, even on 64-bit Windows operating systems. On these systems, the 32-bit Office client is supported as a Windows-32-on-Windows-64 (WOW64) installation. WOW64 is the x86 emulator that enables 32-bit Windows-based applications to run seamlessly on 64-bit Windows systems. This lets users continue to use existing Microsoft ActiveX Controls and COM add-ins with 32-bit Office.” The same advice applies to Office 2010, including the Access 2010 Runtime.)

Hope this helps…

Reply | Quote

Hi Rick,

Thank you again for your help – much appreciated!

I have made some progress, thanks to your most-recent post. I Removed the 64-bit version I’d been trying, and I installed the 32-bit version.

I could see right away that this was the right choice because the Setup took a couple of minutes (unlike the 64-bit Setup which took maybe 3 seconds). Sure enough, I now have the Office 14 (with MSAccess.exe!) folder.

I then tried to open a couple of the .MDBs in question and they do open, but I immediately get this message:

42400-Capture

Unfortunately, I have no idea how to proceed further (when I click “OK” the databases close immediately).

Thanks again,

Alan

P.S. – Sadly, the person who developed these databases a few years back has disappeared.

Reply | Quote

As I said in my post #2, and as jwoods has suggested also, why not try Base in the LibreOffice suite (free)? You will at least be able to get the tables back, even if not the forms or queries. It is quite simple to use as well.

Eliminate spare time: start programming PowerShell

Reply | Quote

Thank you.

I have just installed Libre and indeed its OfficeBase does open the MDB tables so I can view them. This is a great help for me.

Libre does not permit me to open any of the Queries included in the databases, unfortunately, so I’d still like to get the W10 Runtime working.

(BTW, I just found, buried on my hard drive, the Windows 2000 RT version. I recall that it worked for these databases on my W7 PC. Would I have a problem if I tried to install it on my W10 PC as I already have the W2010 RT installed?)[/I]

Thank you again,

Alan

As I said in my post #2, and as jwoods has suggested also, why not try Base in the LibreOffice suite (free)? You will at least be able to get the tables back, even if not the forms or queries. It is quite simple to use as well.

Reply | Quote

Hi Alan,

The error 2544 shows the Access 2010 runtime can’t reference (find) a database object needed to open the database container. I’m at the limit of my Access knowledge here but if you were able to use the database with an earlier version of the Access runtime then there is no harm trying to un-install the Access 2010 runtime and installing an earlier one. A quick Google search shows others having issues with the Access 2010 runtime yet earlier versions of the runtime working for them.

Try the Access 2007 runtime (downloadable from Microsoft here). Have a look here for more info.

Hope this helps…

Reply | Quote

Alan,

I tried this in a Win 10 Virtual Machine:

[*]Install the Access2010 Runtime.
[*]Copy a .mdb file into the VM.
[*]Double Click the .mdb in File Explorer

The file opened right up to the Startup Form after a message about trusted code. That is important as you MUST have the Database set to automatically startup a form that will have the controls to allow the user to navigate w/o the use of the Ribbon.

HTH :cheers:

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

Reply | Quote

Thanks Boyd, I obviously didn’t read the description fully. Would it be true that the database to be opened by Runtime needs to open with a form, and it won’t open if it doesn’t have such a thing? Would it therefore require an autoexec macro to open such a form or is there another way to do this? This may be why AlanB1 couldn’t open his database with Runtime, unlike Rick with his databases.

Eliminate spare time: start programming PowerShell

Reply | Quote

Thanks Boyd, I obviously didn’t read the description fully. Would it be true that the database to be opened by Runtime needs to open with a form, and it won’t open if it doesn’t have such a thing? Would it therefore require an autoexec macro to open such a form or is there another way to do this? This may be why AlanB1 couldn’t open his database with Runtime, unlike Rick with his databases.

The database will always open. If there is not a s form display automatically then you the Access shell with a blank window when the form would be shown.

If you have Access 2007 or later then give it a test by renaming any .accdb (or even a .mdb) to .ACCDR. Then double click it. This forces the full version of Access into Runtime mode. With 2003 and older you have to use the /runtime command line switch.

Reply | Quote

Glad you got it sorted…:D

Eliminate spare time: start programming PowerShell

Reply | Quote

Hey Y’all,

Been following this discussion and testing along the way, here’s what I’ve found.

After installing the 2010 Access RT and double clicking my test .mdb file I got this message:
42421-accessRT-Error
Clicking OPEN my database loaded and it operated as it should.

I then did a little googling based on Boyd’s post and found this:

You can create a trusted location via the registry by following this post #2. Note: change the 12 to match the number of your installed version of the Runtime (in my case 14).

After following the instructions:
42422-RegitEditScreen

Now double clicking my .mdb test file it loaded w/o the message.

HTH :cheers:

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

Reply | Quote

I have an article on the subject of trusted locations here: Trust Center in Access 2007 and 2010 Trusted Locations (Click Here)
*** scroll down to the section: Setting the Trusted Locations when deploying the Access Runtime Version
There you will also find a link to a free tool that will created the trusted location for you call addpath.

Reply | Quote

Hi Guys,

(Sorry if this is a duplicate post – I posted a response 2 days ago, but I don’t see it here.)

Just wanted to update (and thank!) everyone – I think I’m good now.

Here’s what solved the problem for me – I finally found an Access RT2000 version on my new PC (I’d thought it was lost when I got the new PC a few months ago). I Removed the RT2010 version, and installed the RT2000, and the db opened right up (and the queries work too!). I’ve not yet tried the other db but the main one is the biggie.

The RT2000 was distributed by the db’s creator many years ago, and fortunately I saved it (the author has disappeared). I have no idea if the RT2000 is available anywhere else.

Anyway, my great thanks to Rick (and to RetiredGeek and HiTechCoach) for your generous help and time. Much appreciated! I’m glad I found this place (I’ve been a “Win Secrets” subscriber for many years.)

Alan

Reply | Quote

Hi Guys,

(Sorry if this is a duplicate post – I posted a response 2 days ago, but I don’t see it here.)

Just wanted to update (and thank!) everyone – I think I’m good now.

Here’s what solved the problem for me – I finally found an Access RT2000 version on my new PC (I’d thought it was lost when I got the new PC a few months ago). I Removed the RT2010 version, and installed the RT2000, and the db opened right up (and the queries work too!). I’ve not yet tried the other db but the main one is the biggie.

The RT2000 was distributed by the db’s creator many years ago, and fortunately I saved it (the author has disappeared). I have no idea if the RT2000 is available anywhere else.

Anyway, my great thanks to Rick (and to RetiredGeek and HiTechCoach) for your generous help and time. Much appreciated! I’m glad I found this place (I’ve been a “Win Secrets” subscriber for many years.)

Alan

Alan,

You’re welcome. Glad you got it sorted out.

I also have an Access 2003 Runtime install package I used when I deployed 2003 solutions. I did no offer it since Access 2003 and older are no longer supported and are a security risk. For security reasons I highly recommend using Access 2007 or 2010 Runtme.

Reply | Quote