|
|
|
|
|
Rick recently authored “Programming Microsoft
Access 2000” for Microsoft Press |
|
He is a regular contributor to Microsoft Office
and VBA Developer (as well as other computer pubs) |
|
He has lectured on Access/Office topics on 3
continents |
|
|
|
|
Introduction to Package and Deployment issues
with Office 2000 |
|
Review of selected Package wizard screens |
|
Review of selected Deployment wizard screens |
|
Review of Managing Script wizard screens |
|
|
|
|
|
Targeting the
Access Run-Time (with demos) |
|
Deployment Demonstrations |
|
Launching the Package and Deployment Wizard |
|
Deploying an Access app |
|
Deploying an Excel app |
|
Deploying an Access app that references an Excel
spreadsheet |
|
|
|
|
|
|
Since ODE is in beta actual deployment behavior
may vary slightly in final shipping product |
|
Some features do not operate in beta as they
will in the final product (they are incomplete in the beta) |
|
I did not discuss/demo selected interesting new
features because they were not operational – stay tune to Microsoft Office
and VBA Developer for more on these topics |
|
|
|
|
It can simplify the installation of custom
office solutions and make them easier to start using |
|
It can enable you to build stand-alone apps that
incorporate the functionality Access and the MSDE database engines |
|
|
|
|
Access Run-Time |
|
Redistributable MSDE |
|
Other Office components do not offer
royalty-free support; clients must have package to run your app |
|
|
|
|
It ships with Microsoft Office 2000 Developer
Edition ODE |
|
I has three key functions |
|
Starting the wizard can be a multi-step process:
load, start, invoke functions |
|
|
|
|
|
|
Standard Setup Package is for distributing a
normal solution |
|
Dependency File is for setting up component
information for a project (or object) to work in another app |
|
|
|
|
|
|
The Package folder is a repository for files
created by the Package wizard |
|
The screen enables you to select a previously
existing folder or create a new one on your drive or a network drive |
|
|
|
|
List the files automatically included in the
package |
|
Let’s you add other files besides those based on
the current project |
|
Includes Access Run-Time by default |
|
|
|
|
Default is a single CAB for deployment over a
network |
|
You can optionally select one of several floppy
sizes when shipping disks is the preferred way to distribute an app |
|
|
|
|
Accept the default name or assign a new one for
users to reference when they start the app |
|
Designate a command to run after installation –
for example, to load an MSDE database |
|
|
|
|
Allows you to specify a Start Menu item and
folder for your app |
|
You can also specify properties, such as the
run-time option |
|
|
|
|
Allows you to specify files as shared so they
can remain even after removal of an app |
|
Used for files that serve more than one app |
|
|
|
|
Assign a script name to package setup choices |
|
Let’s you re-use selection again to save time on
re-packaging option |
|
Afterwards, you can save a text file documenting
packaging choices |
|
|
|
|
Choose a previously prepared script to re-use,
or |
|
Select none to design a new script that is not
based on prior choices |
|
|
|
|
Designate a folder to hold storage files (for
example, your setup program) |
|
Use a different folder than for Package |
|
|
|
|
Choose either Folder or Web deployment method |
|
Choosing Web brings up extra screens tailored to
its features and requirements |
|
|
|
|
Shows items to appear in your deployment folder |
|
If they do not match your expectations, you may
need to go back and re-package |
|
|
|
|
When you are deploying to a web site, an extra
screen appears for you to add additional files not in the Package |
|
In order to select a file, it must be in the
folder for the project that you are deploying |
|
|
|
|
When deploying via the web, you must name a site
from which you will deploy |
|
Also, indicate a publishing format from the site |
|
|
|
|
Assign a script name to save the choices for
future reference |
|
Afterwards, you can choose to save a text file
summarizing deployment choices |
|
|
|
|
Use the Manage Scripts button on the wizard
screen to gain access to the package and deployment scripts |
|
You can rename, duplicate, and delete scripts |
|
Manage scripts on a project basis |
|
|
|
|
Use the Run-Time Link to see how your project
behaves in run-time |
|
Use Full link to see modify your code and set
startup options |
|
You can deploy either run-time or full versions |
|
Demo for StartMenu |
|
|
|
|
Database, macro, and VBE windows disable in
Run-Time |
|
Built-in toolbars not supported, but custom ones
are supported |
|
Shortcut menus are not available |
|
Errors not trapped shut down app (demo) |
|
|
|
|
Open VBE window of main app |
|
Load Package and Deployment Wizard |
|
Start wizard |
|
Click Package button and pass through screens
(demo) |
|
|
|
|
Go through deployment screens |
|
Install StartMenu app |
|
Operate app |
|
Remove StartMenu app (demo) |
|
|
|
|
Show Chapter 14 and demo native spreadsheet
procedure |
|
Start Package
wizard and show Cab options for multiple or single Cab also show
non-default selection of Access Run-time |
|
Notice how run setup, demo behavior, remove is
same as for Access app (demo) |
|
|
|
|
Describe createTableFromXL procedure |
|
Highlight the desirability of a variable XL file
spec |
|
Run from proc in My Documents folder |
|
Show how to add a file during setup |
|
Run run Start menu – XL spreadsheet is in a
different location |
|
|
|
|
|
Package and Deployment wizard is for custom and
even commercial apps |
|
Use either Full or Run-Time versions of Access |
|
Other Office apps also can be setup |
|
You can setup multiple Office apps, such as
Access + Excel |
|
Easy to deploy, but you should |
|
Test for usability |
|
Test for security |
|
Notes