Wrox Programmer Forums
Go Back   Wrox Programmer Forums > Microsoft Office > Access and Access VBA > Access
Access Discussion of Microsoft Access database design and programming. See also the forums for Access ASP and Access VBA.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Access section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
Old November 19th, 2005, 12:29 AM
Friend of Wrox
Join Date: Mar 2004
Posts: 217
Thanks: 0
Thanked 1 Time in 1 Post
Default install failure of deployment package

I have an .mdb with several Activex controls (Date Time Picker, MS Common Dialog controls ) and other references (to the Word Object model, of course VBA and DAO)associated with it. The file runs FINE on the machines I finished development on (both XP machines which have Office 2K Development Edition) but the deployment package does not install on my machine at work (running Windows 2K, a regular A2K license and no Visual Studio). It goes into install, and when it gets to "installing MSVM60.dll ("7 of 7)" a msgbox says it has to re-start the System. Once re-started, installation does not resume, and the package does NOT complete installation. When you begin install again it runs through the same confirmation screens, and repeats its performance when "installing MSVM60.dll" comes back up.

msvm60.dll is already on my machine. Deleting it, then running Install for the deployment package confirms the package is installing that .dll. Our Tech tried installing the upgrade for msvm60.dll, and that did not solve the problem.

I tried making a NEW deployment package with just a form, table with dummy data and the 2 Activex controls needed, and that installed fine onto the machine. The Date Timepicker works fine WITHIN that one .mdb, but does not allow itself to be used in other .mdbs on the machine. So that "work-around" doesn;t solve it.

1. Does anyone have any suggestions as to what may be going wrong (and how to fix it?)
The next step in the "experiment" is to install XP, but it's a big job that (if possible) we'd prefer to avoid.

2. Do Activex controls register to an individual .mdb? If so, is there a way to "hand register" them? (Or is there another piece of the control that is only available for development?) I was hoping I could use those Activex's in other .mdbs once they were on my machine.

Our final installation is for 2 or 3 machines to use the .mdb, which we'll put on a Share on the server. I'll split the db and we'll put a FE on each machine (with the Activex's) on each machine after I confirm it's working and the forms fit the screens.

Any sugggestions?

Thank you,


Similar Threads
Thread Thread Starter Forum Replies Last Post
Package and Deployment - XLStart Up Shasur Excel VBA 1 January 10th, 2006 02:21 PM
Package Deployment Problem bveerendrakumar Pro VB 6 8 March 16th, 2005 05:05 AM
Child package returning failure vipulcs SQL Server DTS 6 January 10th, 2005 12:26 AM
Package and Deployment rwalker VS.NET 2002/2003 2 February 27th, 2004 09:44 AM

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.