Solved

Access and Runtime

Posted on 2014-01-09
4
317 Views
Last Modified: 2014-01-12
Experts,

What functionality is lost in Runtime?  Can a user enter data and run reports, click buttons with macros?

thank you
0
Comment
Question by:pdvsa
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
4 Comments
 
LVL 12

Accepted Solution

by:
pdebaets earned 250 total points
ID: 39769766
Yes, a user can enter data, run reports and click buttons with macros.

In runtime mode, users will not be able to open Access objects in design mode. They will also not have access to the built-in set of Access toolbars including right-click shortcut menus.

You can test the runtime environment by opening your database with the /runtime switch, or if you have an Access .accdb file, just rename it temporarily to .accdr to do the runtime environment testing
0
 
LVL 84

Assisted Solution

by:Scott McDaniel (Microsoft Access MVP - EE MVE )
Scott McDaniel (Microsoft Access MVP - EE MVE ) earned 250 total points
ID: 39769859
In addition what Peter suggests, see this MSFT article for more info:

http://msdn.microsoft.com/en-us/library/cc136539.aspx

Note that users can install multiple versions of Access on their machine, but be careful with that. If you have users who are running the full version of Access 2003, for example, and you install the 2010 runtime, the runtime can inadvertently be set as the default program to use when launching all Access databases - and that can be a very bad thing when users try to open their 2003 database and create a report!
0
 

Author Comment

by:pdvsa
ID: 39770966
OK thank you both.  Good to know this.  

If the users have run time and I have full version 2010, can I expect issues or will run smoothly...as expected?
0
 
LVL 84
ID: 39775266
There are some "gotchas" with the runtime, but the article I linked above explains them pretty well.

As Peter suggested, you should test your app thoroughly using the /runtime switch, or by changing the extension to ".accdr". This forces Access to run the app as if it's in the Runtime, and you can test it that way.
0

Featured Post

Simplifying Server Workload Migrations

This use case outlines the migration challenges that organizations face and how the Acronis AnyData Engine supports physical-to-physical (P2P), physical-to-virtual (P2V), virtual to physical (V2P), and cross-virtual (V2V) migration scenarios to address these challenges.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Describes a method of obtaining an object variable to an already running instance of Microsoft Access so that it can be controlled via automation.
As tax season makes its return, so does the increase in cyber crime and tax refund phishing that comes with it
In Microsoft Access, learn how to “cascade” or have the displayed data of one combo control depend upon what’s entered in another. Base the dependent combo on a query for its row source: Add a reference to the first combo on the form as criteria i…
With Microsoft Access, learn how to start a database in different ways and produce different start-up actions allowing you to use a single database to perform multiple tasks. Specify a start-up form through options: Specify an Autoexec macro: Us…

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question