bsmiller92 said:
I have an application that I have developed that's used by about 70 users
across the State of Ohio, that has a custom ribbon with command buttons on
it. I use the Access Developer Extensions to package it up and when
installed
and run on my test laptop, that has Access 2007 Runtime on it, the ribbon
shows up in the program, but the command button is grayed out. What do I
need
to do to make the ribbon command work in Access 2007 Runtime?
"command" button is a rather vague term here, as is "many" command buttons
everywhere in access....
Does any command button or forms, or part of the application function
correctly?
Your applciation has to instaleld to a trused location. You can also try
setting your macor securty to low for some testing.
the reg key for macor securty = low is:
Root: HKCU;Subkey:
"Software\Microsoft\Office\12.0\Access\Security";ValueType: dword;
ValueName: "VBAWarnings"; ValueData: "1"
and, the reg key for trused locaitons is:
HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Access\Security
\Trusted Locations\
Location(x)
AllowSubFolders (REG_DWORD) = 1
Path (REG_SZ) "C:\MyDatabaseFolder\"
I was under the impression that when you deploy using the runtime, a correct
trusted location is setup. Regarless, try the above setting the macro
security to low to see if this helps.
As for the access built in ribbons? When you deploy with the runtime you'll
have to build your own custom ribbons, or supply buttons and options on the
forms to make the application function correctly.
The runtime version of access is simply a stripped down version of access
with all the user tools stripped out. It is designed for developers to build
custom applications. Those custom applications must include setting up a
correct user interface. That custom user interface can be something very
simple as having some type of switchboard or startup form launched when the
application loads. That startup form can thus provide the options to run the
application (launch other forms etc). The devloper can also go further down
the road and add things like custom ribbons for the application if need be.
So either way, it is up to the developer of the application when deploying
with the runtime to supply some type of user interface...most of the built
in ribbon interface is not included in the runtime.
