Dev Center

Schließen
Deutschland (Deutsch)
Anmelden
Startseite Produkte Office 365 Library Informieren Downloads Support Foren

- Email Deutsch
- Facebook Deutsch
- Twitter Deutsch
- Digg Deutsch
- Technorati Deutsch
- Delicious Deutsch
- Messenger Deutsch

Freigeben
Office Development
Microsoft Office 2010
Lync 2010
Excel 2010
InfoPath 2010
Office 2010
OneNote 2010
Outlook 2010
PowerPoint 2010
Project 2010
Publisher 2010
SharePoint Workspace 2010
Visio 2010
Word 2010
2007 Microsoft Office System

# Deploying Access 2007 Runtime-Based Solutions

Office 2007
73 von 107 fanden dies hilfreich - Dieses Thema bewerten.

Summary: Learn how to use the Package Solution Wizard to build and distribute solutions that include the Microsoft Office Access 2007 Runtime. (7 printed pages)

Mike Stowe, Microsoft Corporation

June 2007

Applies to: Microsoft Office Access 2007, Microsoft Office Access 2007 Developer Extensions

Download the Access 2007 Developer Extensions.

Download the Access 2007 Runtime.

Contents

- Overview of Runtime-Based Solution Deployment
- Access Developer Extensions
- Deploying Applications Using the Package Solution Wizard
- Package Solution Wizard Output
- Conclusion
- Additional Resources

# Overview of Runtime-Based Solution Deployment

After you create a Microsoft Office Access 2007 application, you must distribute it to users. The Package Solution Wizard, which is included in the Access 2007 Developer Extensions, is designed to make distributing your Access 2007 database solutions easier.

This article reviews the components of the Access 2007 Developer Extensions. These include the Package Solution Wizard, and describes the settings that are available when you create a redistributable deployment package that includes the Microsoft Office Access 2007 Runtime.

# Access Developer Extensions

Table 1 describes the components of the Access 2007 Developer Extensions.

Table 1. Access Developer Extensions Components

###

Component | Description
--- | ---
Package Solution Wizard | Enables you to create a Windows Installer Package (.msi file) that installs your database and any supporting files on the user's computer. Your deployment package can also include the Access 2007 Runtime, or it can prompt users to download the Access 2007 Runtime.
Save As Template add-in | Enables you to create database templates (ACCDTs) that you can feature in the Access 2007 Getting Started page.
Source Code Control add-in | Enables integration with Microsoft Visual SourceSafe or other source-code control systems so that you can check in and check out objects—queries, forms, reports, macros, modules, and data—and see changes that are made to checked out objects.

For more information about the Access Developer Extensions, see Introducing the Access 2007 Developer Extensions Runtime.

# Deploying Applications Using the Package Solution Wizard

The Package Solution Wizard is an add-in that is available as part of the Access 2007 Developer Extensions. It provides a simple way to bundle and deploy Office Access 2007 database applications. The wizard guides you through the steps that are required to bundle stand-alone Access 2007 applications into deployment packages. You can use the Package Solution Wizard to include the Access 2007 Runtime in your packages and to create shortcuts that start the appropriate Access file. The output of the Package Solution Wizard is a Windows Installer (.msi) Setup file that guides users through the installation of your Access application.

After you create an Office Access 2007 application (.accdb, .accde, .accdr, .mdb, .mde, .adp, or .ade), you can deploy the application to users who do not have Access 2007 installed by distributing the application together with the Access 2007 Runtime. The Access 2007 Runtime is a version of Access 2007 in which the design-time features are disabled. For more information about the Access 2007 Runtime, see Introducing the Access 2007 Developer Extensions and Runtime.

This section examines the settings that are available in the Package Solution Wizard. To start the Package Solution Wizard, click the Microsoft Office Button, click Developer, and then click Package Solution.

#### Wizard Templates and Output Options

On the first page of the Package Solution Wizard, you can decide to use the settings from a previous use of the wizard as a template. To do this, click Load wizard settings from a saved template file.

Note:
To save the current Package Solution Wizard settings as a template, click Save Wizard Settings on any Package Solution Wizard page. The next time that you start the wizard and decide to use a saved template, the wizard pages are pre-populated with values from the template.

Under Output Options, the Destination folder setting specifies the folder in which the deployment package will be stored.

Figure 1 shows the available options on the first page of the Package Solution Wizard.

Figure 1. Wizard Template and Output Options

#### Installation Options

Page 2 of the Package Solution Wizard contains the following Installation Options settings:

- File to package specifies the path and file name of the Office Access 2007 database that you want to include in the deployment package.
- Root install folder and Install subfolder specify the folder location where your application will be installed.
- Pre-installation requirements lets you specify if you want to require that users have Office Access 2007 installed before your application can be installed, or if they have to use the Access 2007 Runtime. Table 2 describes the available options.

  ### Table 2. Pre-installation requirements settings

  Setting | Description
  --- | ---
  Require Microsoft Office Access 2007 to be installed | Access 2007 must be installed on the computer before your application is installed. If it is not, users receive an error message that explains that they must install Access 2007 before they install the application.
  Require the Access 2007 Runtime to be downloaded if Access is not already installed | If Access 2007 is not installed, users must download the Access 2007 Runtime. The file name extension of the database that you specify in the File to package box is changed to .accdr to ensure that your database always opens in run-time mode (see Figure 2). If users try to run the installation package without having Access 2007 or the Access 2007 Runtime installed, they receive an error message that includes a URL where they can download the Access 2007 Runtime.
  Require nothing and install the Access 2007 Runtime | The Access 2007 Runtime will be installed with your application, even if Access 2007 is already installed. Specify the location of the AccessRuntime.exe file on your computer in the Access 2007 Runtime setup package text box. The file name extension of the database that you specify in the File to package box is changed to .accdr to ensure that your database always opens in run-time mode (see Figure 2).

Figure 2 shows the Installation Options settings as they appear on the second page of the Package Solution Wizard.

Figure 2. Installation Options

The Shortcut Options section on this same page contains settings that configure the shortcuts to be installed on the destination computer that has your application.

- Install Locations specifies where a shortcut to your application will be created when the application is installed.
- Shortcut name and Icon settings specify the display name and icon for the shortcut.
- Startup macro and VBA Command value settings specify the name of a macro or a Visual Basic for Applications (VBA) procedure that runs every time that your application is loaded.

Figure 3 shows the Shortcut Options on the second page of the Package Solution Wizard.

Figure 3. Shortcut Options

#### Additional Files and Registry Keys

Page 3 of the Package Solution Wizard contains the Additional Files section, which you can use to add any file outside the database that your application depends on. For example, you might want to include a readme.txt file or some sample files for your application. To add these files, click Add, and then select the files.

In the Additional Registry Keys section, you can specify any Windows Registry keys that you want to be created when your application is installed. When you specify a registry key to be added to the All Users root, you should prefix the key with Software\. If you do not do this, users might receive an error message when they install the application.

Figure 4 shows the Additional Files and Additional Registry Keys sections on the third page of the wizard.

Figure 4. Additional Files and Additional Registry Keys Options

#### General Properties, Feature Information, and Advanced Options

Page 4 of the wizard contains the following settings under General Properties:

- Product Name specifies the name of your application.
- Install Language specifies the language to be displayed when users install your application.
- End user license agreement (EULA) specifies the location of the license terms file to include with your application. The license terms file must be in Rich Text Format (.rtf).

This page contains the following settings under Feature Information:

- Feature Title specifies the title of the feature displayed when the user selects the Custom option while the user installs your application.
- Feature Description specifies the description of the feature displayed when the user selects the Custom option while the user installs your application.

Figure 5 shows the General Properties and Feature Information sections that appear on the fourth page of the wizard.

Figure 5. General Properties and Feature Information

In the Add/Remove Programs Information section of the wizard, shown in Figure 6, you can specify the information that appears when users click Click here for support information for your application in Add or Remove Programs in Control Panel.

The File Properties for the Windows Installer Package section of this page lets you specify information that appears when users right-click the setup (.msi) file and then click Properties.

Page 4 of the wizard contains the following settings under Advanced Options:

- Background Image specifies the image that you want to appear as the background of your installation program. For example, the image could be a .jpg file or a .bmp file that displays your company logo.
- Product Code specifies a unique identifier for a particular product release, represented as a string GUID.
- Upgrade Code specifies a GUID that represents a related set of products. The Upgrade Code is used to search for related versions of the product that are already installed.

Figure 6 shows the Add/Remove Programs Information, File Properties, and Advanced Options on page 4 of the wizard.

Figure 6. Add/Remove Programs Information, File Properties, and Advanced Options

# Package Solution Wizard Output

When you click OK on the last page of the Package Solution Wizard, the deployment package is created. This package contains all the files that are required to install your application. The package is created in the folder that you specified in the Destination folder setting on page 1 of the wizard.

The root folder of the deployment package contains two files: Setup.exe and Autorun.inf. Setup.exe is used to start the installation of your application. Autorun.inf. specifies what happens when the user inserts a CD that contains your application. By default, the Setup.exe file runs automatically.

The Files subfolder of the deployment package contains the .msi file that the wizard created. The Files subfolder also contains the AccessRuntime.exe file if you specified that your application should execute in run-time mode.

You can copy the deployment package to a CD, or put it on a shared network location.

# Conclusion

This article briefly describes the components that make up the Access 2007 Developer Extensions. It also describes the settings that are available when you use the Package Solution Wizard to create an Access deployment package and include the Access 2007 Runtime. The Access Developer Extensions components that include the Package Solution Wizard, can make deploying and working with your Access 2007 solutions much easier.

# Additional Resources

For more information about Access 2007, the Access 2007 Developer Extensions, and the Access 2007 Runtime, see the following resources:

- Access Developer Portal
- Introducing the Access 2007 Developer Extensions and Runtime
- Access 2007 Resource Center
- Microsoft Office Developer Center

Fanden Sie dies hilfreich? Ja Nein
Nicht genau
Keine ausreichende Tiefe
Weitere Codebeispiele erforderlich
Die Übersetzung sollte verbessert werden.
Bitte machen Sie weitere Angaben.
(1500 verbleibende Zeichen)
Community-Hinzufügungen HINZUFÜGEN
What if Access 2003 is already installed?
It appears that if a previous version of Access (say, a full version of Office) is already installed, then installing the Access 2007 runtime can cause problems. Is there anyway to prevent the installation of Access 2007 from taking place if a specific previous version is already present on the client computer?
[tfl - 29 04 12] Hi - and thanks for your post. Community content is not the appropriate place for technical support queries. Instead, you should visit the MSDN Forums at http://forums.microsoft.com/MSDN, where such posts are welcomed and where you stand a much better chance of getting your query resolved. Sorry if that's not the answer you wanted to hear.
Thomas Lee
4/29/2012
Run Linked Table Management in an Access_fe.ACCDR
Access 2007 Developer Extension and Runtime:
1)
When deploying, I need to reconnect to a different Access back-end Database.
The toolbar option is gone.
Tried by a startup macro - error occured and shut down (!!??)
How to?
2) How run the Link Table Management by VB Code?
[tfl - 29 04 12] Hi - and thanks for your post. Community content is not the appropriate place for technical support queries. Instead, you should visit the MSDN Forums at http://forums.microsoft.com/MSDN, where such posts are welcomed and where you stand a much better chance of getting your query resolved. Sorry if that's not the answer you wanted to hear.
Thomas Lee
4/29/2012
Access 2003 Already Installed is a Big Problem!
Previous Access 2003 databases do not run correctly until Access 2007 Runtime is uninstalled and repair of Access 2003 is accomplished.
[tfl - 29 04 12] Hi - and thanks for your post. Community content is not the appropriate place for technical support queries. Instead, you should visit the MSDN Forums at http://forums.microsoft.com/MSDN, where such posts are welcomed and where you stand a much better chance of getting your query resolved. Sorry if that's not the answer you wanted to hear.
Thomas Lee
4/29/2012
Upgrading a Package

I would like to know how to upgrade a package solution from access 2007, I did some major changes like creating several forms, changing the database tables and some code with VBA.
How can I upgrade the msi already installed in one computer?

[tfl - 29 04 12] Hi - and thanks for your post. Community content is not the appropriate place for technical support queries. Instead, you should visit the MSDN Forums at http://forums.microsoft.com/MSDN, where such posts are welcomed and where you stand a much better chance of getting your query resolved. Sorry if that's not the answer you wanted to hear.

Thomas Lee
4/29/2012
Setting network datafile target for Access 2007 runtime
I'm creating a POS application for a business, and I frequently need to be able to reset the path to the shared data .MDB on that network. Can I do that if I only have the 2007 Runtime in the environment, and, if so, how?
[tfl - 29 04 12] Hi - and thanks for your post. Community content is not the appropriate place for technical support queries. Instead, you should visit the MSDN Forums at http://forums.microsoft.com/MSDN, where such posts are welcomed and where you stand a much better chance of getting your query resolved. Sorry if that's not the answer you wanted to hear.
Thomas Lee
4/29/2012
OK button is disabled on the last (4th) wizard page
I've just filled all textboxes on the fourth page of the wizard. OK button is still disabled
What's the matter?
I'm also come across this problem, can anyone help?
[tfl - 29 04 12] Hi - and thanks for your post. Community content is not the appropriate place for technical support queries. Instead, you should visit the MSDN Forums at http://forums.microsoft.com/MSDN, where such posts are welcomed and where you stand a much better chance of getting your query resolved. Sorry if that's not the answer you wanted to hear.
Thomas Lee
4/29/2012
Creating a shortcut with the package solution
I use a workgroup file for an application I developed, the shortcut "Target" path should contain "MSACCESS.EXE path" &lt;&gt; "ACCESS Application file name and path"&lt;&gt; /switch "Workgroup file path"
Also the Start In path is "ACCESS Application file folder"
How can I create the shortcut using code during the installation?
I tried a couple of times with the developer packager but it omits Start In and adds info in target that throws off the order required for the Target path and workgroup file information.
Any input is greatly appreciated.
Regards,
Manny
[tfl - 29 04 12] Hi - and thanks for your post. Community content is not the appropriate place for technical support queries. Instead, you should visit the MSDN Forums at http://forums.microsoft.com/MSDN, where such posts are welcomed and where you stand a much better chance of getting your query resolved. Sorry if that's not the answer you wanted to hear.
Thomas Lee
4/29/2012
How to protect Microsoft Access 2007 database from copying
How to protect Microsoft Access 2007 database from copying
[tfl - 29 04 12] Hi - and thanks for your post. Community content is not the appropriate place for technical support queries. Instead, you should visit the MSDN Forums at http://forums.microsoft.com/MSDN, where such posts are welcomed and where you stand a much better chance of getting your query resolved. Sorry if that's not the answer you wanted to hear.
Thomas Lee
4/29/2012
Is Access 2007 Runtime compantible with 64 bits
I guess based on my experience the answer is no.
Well unless you DONT have installed the Microsft Office 2007.
I had deployed a 2007 DB (TLOKEN©) with runtime running on a 64 bits PC
The user installed MS/Office and the application TLOKEN©, didnt work anymore
doint some troubleshouting, the MSOfficce uninstalled / reboot and the aplication installed... It worked
SO I guess runtime 07 and MS-office 07 installed both in 64 bits, are sharing libraries/resources that are not compatible
HOPEFULLY MICROSOFT RELEASES A NEW PATCH FOR 32 and 64 BITS
THANKS
PAKO BS
7/18/2011
Broken references don't appear to be fixable as the documentation suggests
If the Access 2007 project has references for ADODB and ADOX, and the packaged project and runtime are installed on an XP machine with Office 2003, then you cannot add the references to the 2003 versions of ADODB and ADOX until you remove the broken references to the 2007 versions. This would be simple to achieve if you could get at the tools/references menu in teh VB editor, but of course you can't as it is using runtime.
So this has to be done in code as the msdn article on Reference.Remove explains. However, although the GUID of the broken reference can be retrieved (as explained in the article), the name and full path cannot be retrieved and the Reference.Remove method does not work. I have left a note on the relevant page on this site explaining how I went about this but I think that the bottom line is that this is a straightforwad bug.
Hugh Meares
3/21/2010
Installer Language

How can I change the Installer Language when I make an installer package?
The English is working, but I need Hungarian.
Thanks
Red
.

    [tfl - 10 06 09] Hi - and thanks for your post. You should post questions like this to the MSDN Forums at http://forums.microsoft.com/msdn or the MSDN Newsgroups at http://www.microsoft.com/communities/newsgroups/en-us/. You are much more likely get a quicker response using the forums than through the Community Content. For specific help about:
    Visual Studio  : http://groups.google.com/groups/dir?sel=usenet%3Dmicrosoft.public.vstudio%2C&
    .NET Framework : http://groups.google.com/groups/dir?sel=usenet%3Dmicrosoft.public.dotnet.framework
    All Public     : http://groups.google.com/groups/dir?sel=usenet%3Dmicrosoft.public%2C&

boertjebartje63
1/26/2010