How do I open access in runtime without security warnings?
I have been able to upgrade successfully except for the Security Warning I get when opening the database in runtime.
Have tried changing settings in the Trust Centre, this has fixed the Full Access security but seems to have no effect on Runtime.
Thank you for taking the time to report an issue.
What's wrong... Please write below.
The users on runtime can use the database with no warnings however if they have the database open and then I open it I get the warning "you do not have exclusive access." It may have something to do with the fact that today I was making some changes and someone popped it open on me through the runtime.
I keep seeing warnings about using the automatic compact and repair in the Access Options of 2007. However, I'm worried about data bloat if this is never done.
Does anyone out there have experience with Access 2007 Runtime using the automatic compact and repair?
Instructions on runtime packaging tell me that a Developer option should appear in the resulting drop-down when I click the Office button (top-left round thing) when I have a d/b open in Access. It's not there! I have un-installed and re-installed the extensions and the runtime - still nothing!
I do have Runtime 2002 (XP) on the same PC, is that relevant?
method 1: access 2010 runtime
method 2: user log in system with multiple security levels .
I want to know if there is any issue with the vba & macros in access 2010 runtime ?
and how to implement multiple users with multiple user security levels . ?
If you are creating an application that runs in an Access Runtime environment, you must carefully consider how to provide an interface for the user. You must also consider the fact that some users may own the correct version of Access and run the application in a full Access environment. Take care to test your application under both environments to make sure it properly balances usability in the Access Runtime environment with code security in a full Access environment.
Of three cases, all of the machines had a previous Access Runtime version installed. In one of these cases I removed the runtime and installed the latest version.
After that I repaired Office Web Components and it worked. This fix did not work on the other two machines. Why?