Installsheild comes with a pretty complete library of merge modules to install lots of different Microsoft (and other) technologies. For example, to include DAO 3.5 and DAO 3.6, all you need to do is select those components from a list of re-distributable modules. All of the details (including the exceptions for different operating systems) are encapsulated within the merge modules. What I seem to be finding out is that unless you are using installsheild, you have to build your own merge modules which means figuring out all the details.
There are several error messages that relate to a missing file or to a file that has a different version from the version that is used in the database. In most cases, you can search the Microsoft Knowledge Base for an article about the specific error message, and you can then resolve the error by following the steps in the article. In some cases, a dependency file is not correctly matched with the primary file.
Creating a new, blank database and then importing objects from another database file can create reference issues if the code or ActiveX controls rely on references that are not included in a database by default. The default references for an Access 2000 database are:
If you converted the database from an earlier version of Access, and the database contains a reference to the Utility.mda file, in most cases you can remove this reference because the functions that this reference calls are included in the default references in Access 2000. If there are references to earlier versions of DAO, you can also remove these references because DAO 3.6 can address these functions.
There are two basic database file distribution methods. You can copy the file from the development computer to the target computer, or you can use the Package and Deployment Wizard to create a setup package.
If you copy the file from the development computer to the target computer, only the database file is copied. You must manually ensure that all files that are listed in the reference list are available, at the correct version level and in the same relative location on the target computer as on the development computer.
A Missing flag, which you may see when you open a module in Design view and then click References on the Tools menu, indicates that the reference to the Common Dialog control on the target computer does not match the source in the database file from the development computer.
Generally, a download manager enables downloading of large files or multiples files in one session. Many web browsers, such as Internet Explorer 9, include a download manager. Stand-alone download managers also are available, including the Microsoft Download Manager.
The Microsoft Download Manager solves these potential problems. It gives you the ability to download multiple files at one time and download large files quickly and reliably. It also allows you to suspend active downloads and resume downloads that have failed.
- Installed Office 97- Wrote some code in VBA for Excel which will use an access database- Got a \"Run-time error '429': ActiveX component can't create object\"- Searched dejanews and Microsoft newsgroups for help- Got the following URL's [ST_rn=ps]/getdoc.xpAN=362644416&search=thread&threaded=1&CONTEXT=919523598.2027618369&HIT_CONTEXT=919523560.1955070234&hitnum=2 - In one of the \"supposed\" solutions to this problem, one had to uninstallOffice 97, but simply uninstalling does not do the trick apparently, becauseyou must use the Office 97 Uninstall utility (see below) _SRV=http%3A%2F%2Fwww.microsoft.com&Boolean=PHRASE&SearchArea=&intCat=4&SName=MSDN&SPath=%5Cpremium%5Cmsdn%5Clibrary&Cluster=&SearchString=Registry+Eraser+Utility&Finish.x=18&Finish.y=8 - OK, uninstalled office.- Installed again- Tried to apply service packs again- Guess what I'm told that the service packs can't be applied (neither SR-1nor SR-2) since the service pack installation thinks they're alreadyinstalled (yeah, sure)- So, this means that even using the \"special\" uninstall utility, it doesnot completely remove Office 97. (A ploy by Microsoft to make sure that onceOffice is installed, it can never be removed from the system - KnowingMicrosoft all too well, this is the most likely explanation)- Tried to run the code again after installing- Same error 429- Yes, the references are in place (DAO 3.51)- No, there is no error in my code - the code is too simple and I even usedthe automatic typing completion box to fill in the object hierarchy. Toillustrate, the code below is what causes the error (the single line in thesub test() )Dim dd As DAO.DatabaseDim ww As DAO.WorkspacePublic Sub test()Set ww = DAO.DBEngine.CreateWorkspace(\"\", \"admin\", \"\", dbUseJet) 'erroroccurs hereEnd Sub- MICROSOFT - PLEEEEEEASE PROVIDE A SOLUTION - EXTREME FRUSTRATION--Please remove the UPPERCASE characters from my e-mail address for the realthing
I had problems installing/redistribute DAO 2.5 som years ago (error Can'tcrate object) and the problem could be solved with a license key inregistry. I got the key from a computer with VB enterprise editioninstalled, probably not legal but it workt.Your problem might be something else !Is it the DBEngine object och the Workspace object that causes the errorCheck if you get any response on DBEngine.Version in immidiate window.Have you tried the default workspace object, DBEngine.workspaces(0)You can also try register the dao*.dll:s manually with regsvr32.exe./PierreCesar Mugnatto wrote in message ...
Excuse me if I've mistaken what your problem is.......but I copied yoursample code into an Excel VBA session and it ran fine. Well, it doesn't domuch but it didn't cause an error either. I wonder if you had forgotten toadd a reference to Microsoft DAO in the Excel VBA project Without wishing to teach you to suck eggs...... in Excel VBA editor clickon Tools....References and ensure that there is a tick/check against thebest Microsoft DAO Object Library that you have installed. This will makethe DAO stuff available to your Excel session.This might help.Byeeeeeeee !-- Dave SheaReel To Reel LimitedPengeLondon(To reply by eMail, please remove BOZO from my mail address)Cesar Mugnatto wrote in article...
You can download MSXML4MSMS.EXE from Microsoft to get ready-made merge modules for installing Microsoft XML Parser Version 4.0 Service Pack 2. It is available in several languages. Service Pack 2 is a complete replacement and security patch of MSXML 4.0 and MSXML 4.0 Service Pack 1; however, keep in mind that version 4 does not take the place of the XML Parser versions 3.0 and 2.0.
Note: Microsoft no longer recommends the use of these merge modules. Quote: \"Desktop Engine (MSDE 2000) SP3a provides merge modules to support existing applications that use merge modules. The Setup utilities for new applications should be written to call the MSDE 2000 Setup utility instead of directly consuming the MSDE 2000 merge modules.\" The recommended method to redistribute MSDE 2000 is to run MSDE's setup.exe from a bootstrapper program before your actual installation starts.There are several versions of MSDE 2000 merge modules (listed in chronological order): SQL Server 2000 CD includes MSDE merge modules which include several known bugs SQL server refresh CD (Nov 2000 - English) build 194.05 includes some bug fixes for the merge modules Knowledge base articles Q274224 and Q281184 include some hot fixes that became available after the refresh cd was released MSDE 2000 SP1 CD includes updated merge modules that will install MSDE on a machine without having to patch it MSDE 2000 SP3 download, includes fix for SQLSlammer worm MSDE 2000 SP3a download, includes various fixes and improvementsHow to obtain MSDE 2000 SP3a: Download from Related information: Customizing MSDE 2000 Installation Embedding MSDE 2000 Setup into the Setup of Custom Applications (instructions and FAQ by Microsoft) Microsoft SQL Server 2000 Desktop Engine (MSDE) Installation, Deployment, and Patching (Microsoft Support WebCast) SQL Server homepage
According to , the CD can be purchased or is free to download for MSDN customers. It includes apci.msm for 12 different languages (1028, 1031, 1033, 1036, 1040, 1041, 1042, 1043, 1046, 1053, 2052, 3082).Thanks to Troy Phillips
Service Pack 6 for Visual Studio 6 includes 43 language independent merge modules and 2x 34 localized modules for German and Japanese. They supersede the modules in Visual Studio 6 SP 5. Thesemerge modules are also available as separate download.
Service Pack 5 for Visual Studio 6 includes 43 language independent merge modules and 2x 34 localized modules for German and Japanese. They supersede the modules that came withVisual Studio Installer 1.1 and VS6 SP4 (see below). Thesemerge modules are also available as separate download.
Visual Studio Installer 1.1 includes 43 languageindependent merge modules and 2 x 34 localized modules for German and Japanese. The samemodules are included in Service Pack 4 for Visual Studio. They supersede the modules thatcame with Visual Studio Installer 1.0 (see below). These mergemodules are also available as separate download.
VSI 1.0 came with 43 merge modules, which repersent the Service Pack 3 level of VisualStudio. These files have been superseded by the MSMs included in VSI 1.1 and in ServicePack 4 for Visual Studio 6.0, but are still available for download.
Rainbow Technologies have created merge modules to install the drivers for theirSentinel Hardware Keys. They are included in the Sentinel System Driver CD which is alsoavailable for download (select the Full CD option).
MDAC merge modules are included in the setup authoring tools from InstallShieldSoftware Corporation (InstallShield Developer, InstallShield Express, etc.) and WiseSolutions Inc. (Wise for Windows Installer, etc.) 1e1e36bf2d