Where did my Access runtime go?

[VicM]

Hi all,


And a Happy New Year.

I'm using Access 2010, 32-bit.

I created a DB that I want to distribute to family & friends for their use. Because no one has full blown Access, I want to distribute the DB with runtime.

But I first wanted to test out how the DB responds under runtime. So I downloaded the 2010, 32-bit version of runtime and clicked on it to install. It processed the install and said it was complete. When I check my installed programs, it's listed there. However, I don't know where it is on my PC.

I've tried doing a full search and find several folders and files indicating AccessRT. Mostly all these files are .XML files.

There is one .cab file as well. When I look into the .cab file I see MSACCESS.exe. If I click on it, it asks if I want to install. I thought I already did that, so I backed out of it.

Can anyone shed light on where the runtime version might be lurking?

Thanks,
Vic

[CJ_London]

if you have the full version of access, you don't need runtime - instead rename your file as a .accdr - when you open it you will be in runtime mode.

[VicM]

Thanks Ajax, that was helpful.

So when I send family/friends a copy of the runtime install program, do I also send the .accdr or the .accdb file? Or does the .accdr DB inherently contain the runtime and no need to send the runtime install program?

[moke123]

Ideally, you should provide them with a compiled AccDE.
Yes, you can send the runtime or they can download and install themselves.

[CJ_London]

as moke says, you can send whichever you want - they can then download their own runtime application. Whichever you send and especially if you send a .accde, make sure they download the right version - 32bit access 2010 if your tag details are correct. If they download the 64bit version or they happen to have a full 64bit version, your app won't work.

When testing your runtime (using .accdr) be aware that certain features are not available. In particular the ribbon, navigation window and right click menus. If your app relies on these features then you will need to write your own version as an alternative. Depends on what your app is intended to do, but also recommend you split it as recommended by MS. In the event that you have to modify/update the front end you can just send them the updated version. Otherwise if you don't split it, they will lose all their data or you will have to provide a fairly complex routine to copy their data into your updated copy.

Edit: Note the runtime files are quite large - so if planning to email it you may find it exceeds the permitted file size for some recipients email provider - hence better to provide them with a link to the appropriate download page with clear instructions what to do.

[VicM]

Ajax & moke,

Thanks for your suggestions.

Ajax, I already did split the DB, aware of the need to have the workings separate from the data in the event I need to make changes or correct errors.

As for the backend, can I also publish that as .accde along with the frontend? And if I do that, I'm assuming I'm going to have to re-point the frontend to the backend since the backend will have a different extension. Am I correct in that assumption?

Thanks,
Vic

PS: When I worked in industry, I never had to launch runtime. All the clients had full versions of Access. So I'm a bit out of my depth here. LOL

[CJ_London]

As for the backend, can I also publish that as .accde along with the frontend?

you can, but there is zero benefit since .accde only protects forms, reports and vba code. Not tables (or queries for that matter) Not sure about macro's as I don't use them

I'm assuming I'm going to have to re-point the frontend to the backend since the backend will have a different extension. Am I correct in that assumption?

yes - and runtime does not have access to the linked table manager. If these are going to be single users, then you can instruct your users that the backend must be in the same directory as the front end - then you can have some simple code to check if the linked tables are correctly linked and if not relink to the back end making reference to the front end path property (currentproject.path). Plenty of examples on this and other forums about relinking backends.

[VicM]

Thanks Ajax. I think I'm good to go.
Vic