Windows desktop properties and an Access 2003 Runtime Application

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I've packaged a runtime application using MS Access 2003 and the develeper
extensions available in Visual Tools. When I install my application on a
target machine, the menu's in the application are not displaying all of the
options (I think the runtime version has reverted back to the Access default,
where only the most recently used menu options are visible). Is there any way
I can change this ?

I also note that the application background colour is not being picked up
from the windows desktop properties on the target machine (instead it just
displays a grey colour, which I assume is the default).

Is there any way to change this?

Any help on Access runtime or Windows Package Installer is also much
appreciated.

Regards

Byz
 
Hi.
When I install my application on a
target machine, the menu's in the application are not displaying all of the
options (I think the runtime version has reverted back to the Access default,
where only the most recently used menu options are visible). Is there any way
I can change this ?
Click to expand...

The runtime version of Access doesn't include the retail version's built-in
menus. The developer must create custom commandbars to duplicate this
functionality. You'll also find that the error handling must be more robust
for a runtime version database than is required of a database application
designed to be used in the retail version, because any unhandled or
mishandled errors will crash the application.
I also note that the application background colour is not being picked up
from the windows desktop properties on the target machine (instead it just
displays a grey colour, which I assume is the default).

Is there any way to change this?
Click to expand...

WYSIWYG, unless your application programmatically changes the user's
computer's system settings, which is not recommended.
Any help on Access runtime or Windows Package Installer is also much
appreciated.
Click to expand...

Most developers use a third-party packager, such as Wise, SageKey or
InstallShield, to avoid the many hassles and shortcomings of the Package &
Deployment Wizard.

http://www.wise.com

http://www.sagekey.com

http://www.InstallShield.com/

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)

- - -
When you see correct answers to your question posted in Microsoft's Online
Community, please sign in to the Community and mark these posts as "Answers,"
so that all may benefit by filtering on "Answered questions" and quickly
finding the right answers to similar questions. (Only "Answers" have green
check-marks.) Remember that the best answers are often given to those who
have a history of rewarding the contributors who have taken the time to
answer questions correctly.
 
Back
Top