Advanced Registry Cleaner PC Diagnosis and Repair
You won't find the Registry Editor on the Start menu. As it's not something that Microsoft wants the average user to fool around with, the only way to launch it is via the Run dialog box. 2. Type regedit or regedt32, then click OK. The Registry Editor is displayed. Figure 18-1 shows the Registry Editor with the HKEY_CURRENT_USER hive (the purpose of which is explained in Registry Organization, below) expanded to show some of its keys, subkeys, and values. You can think of keys and subkeys as being like the hierarchy of folders and subfolders in the Windows file system. As its name suggests, a value is a named container for a single piece of information, such as the width of a menu. The Registry Editor's right-hand pane shows the values contained within the subkey selected in the left pane. With the exception of a default value that is present in every subkey, each value has its own unique name. The icon to the left of each value indicates its data type.
Use the Additional Registry Keys group to create specific registry keys when the package is installed. Clicking the Add button creates a new record for the registry key. You can set the following values for custom registry keys Key The registry key that will be created. Selecting an existing key in the Additional Registry Keys group and clicking Remove will remove the key from the installation package options. Once all of the Additional Files and Additional Registry Keys have been selected, click Next to continue.
Another option for storing literal values is the Windows registry. In fact, if you browsed the registry using the Registry Editor, you'd see that this is a common way for Windows programs to store configuration information. In Figure 13.4, you can see some of the registry settings used by Excel. NOTE To view the registry, choose Start Run, type regedit, and click OK. WARNING Use extreme caution using the Registry Editor. Never modify registry information unless you are 100 percent sure of the consequences. Individual settings in the registry are referred to as keys. VBA provides a few functions for writing to and reading from the registry. The function SaveSetting creates a new registry key or updates an existing registry key. The function GetSetting retrieves the value associated with a registry key. I'll let you take a stab at what DeleteSetting does. Finally, a function called GetAllSettings retrieves a list of keys and the values associated with a certain application and section....
Prior to Windows NT, Regedit.exe was a 16-bit application for editing the Registry on 16-bit Windows platforms. It was included in Windows NT and 2000 for backward compatibility, but due to its limited functionality under the 32-bit environment, Microsoft recommends that you use Regedit.exe only for its search capabilities on Windows NT 4.0 and Windows 2000. Note Microsoft rewrote RegEdit.exe as a 32-bit application for Windows XP and Windows Server 2003, so, on those platforms, RegEdit.exe is the preferred 32-bit Registry Editor.
Add files and Registry keys, 615 application startup options, 613-615 installer's experience, 615-618 (optional) modify install package (MSI), 620-627 package to create, 611-613 save the template create batch file, 619-620 set installer package properties, 618-619 template, identifying, 610-611 ParamArray, 300 Parameter object properties Direction, 694 Name, 694 Type, 694 Value, 694 parameter query, 189 Parameters collection methods, 694 properties, 694 Parameters collection, methods of AbsolutePage, 722 AbsolutePosition, 722 RegEdit.exe, 576 Regedt32.exe, 576 Registry accessing Registry, 576 controls, 575-576 function of, 574-575 organization, 576-581 Registry Editor RegEdit.exe, 576 Regedt32.exe, 576 Registry functions declaration, 910-911 Registry hives HKEY_LOCAL_MACHINE, 575 HKEY.USERS, 575 Registry organization HKEY_CLASSES_ROOT, 577 HKEY_CURRENT_CONFIG, 581 HKEY_CURRENT_USER, 577-580 HKEY_LOCAL_MACHINE, 580 HKEY_USERS, 580 RegOpenKeyEx function, 592 RegSetValueEx function, 592...
Most Windows applications use the Windows Registry database to store settings. (See Chapter 4 for some additional information about the Registry.) Your VBA procedures can read values from the Registry and write new values to the Registry. Doing so requires the following Windows API declarations If you want to use the Windows Registry to store and retrieve settings for your Excel applications, you don't have to bother with the Windows API calls. Rather, you can use VBA's GetSetting and SaveSetting functions.
The most recently used settings are stored in the Windows Registry. When the user clicks the Close button, the code uses VBA's SaveSetting function to save the value of each control. When the Text Tools utility is started, it uses the GetSetting function to retrieve those values and set the controls accordingly. In the Windows Registry, the settings are stored at the following location Figure 16-5 shows these settings in the Windows Registry Editor program (regedit.exe ). Figure 16-5 Use the Windows Registry Editor program to view the settings stored in the Registry. Figure 16-5 Use the Windows Registry Editor program to view the settings stored in the Registry.
The path contained here determines the location in the Registry where the connection information will be stored. User-specific data source locations are stored to the following registry key and are available only to the current user Odd but true HKCU has a proper case Software node, while HKLM has an uppercase SOFTWARE node. The registry is case insensitive, so it would be okay to make these consistent, although you will see the different cases when you open the registry editor UI.
As you'll see, VBA only supports four native Registry functions, which allow you to store, retrieve, and delete values from one specific area of the Registry. To do anything more advanced, you'll need to use the Windows Registry APIs. If you don't feel confident with API programming, you should first peruse Chapter 13, Extending VBA with APIs, which will give you the background you'll need to understand the more advanced topics in this chapter.
This section describes the Win32 Registry API functions you can use to access and manipulate a wider range of Registry keys than you can with the inbuilt VBA functions. Before attempting this section, however, we strongly advise that you read Chapter 14, Extending VBA with APIs.
Creates or saves an entry for a VB application in the Windows registry. Rules at a Glance Since it writes to the current user's registry key, SaveSetting should be used exclusively for storing user settings it shouldn't store nonuser information (i.e., hardware information, system-level information, or application information that is independent of the user). GetSetting, GetAllSettings, and SaveSetting allow you direct access to only a limited section of the windows registry, that being a special branch created for your application (HKEY_CURRENT_USER Software VB and VBA Program Settings yourappname). You can't access or change other registry settings without resorting to the Windows API. SaveSetting doesn't allow you to write to the default value of a registry key. Attempting to do so produces runtime error 5, Invalid procedure call or argument. This isn't as great a limitation as it may appear, since GetSetting also can't retrieve a default value from a...
Find out the control's ProgID, a unique string used by the Windows operating system (and stored in the Windows registry) for identifying the control's type. If you want to add an ActiveX control (a non-intrinsic control) to the Controls Collection, you'll either need to have some documentation at hand or you'll need to do some investigation in the Windows Registry. In order to find the ProgID for a control's type in the Windows Registry, you can run Regedit from the Start Run menu option of your Windows desktop. Perform an Edit Search in Regedit for the name of the control. Repeat the search with the F3 key until you find the ProgID entry (see Figure 4.15). You can use this key with the Add method. Finding a control's ProgID in the Windows Registry using the Regedit utility. Finding a control's ProgID in the Windows Registry using the Regedit utility.
The Package Solution Wizard is an extremely handy tool for building Access application installation programs. It creates a standard Microsoft Windows Installation package (MSI) file that can perform a number of useful setup tasks, such as deploying Access Runtime and developer-specified application files, adding Windows System Registry keys, and even including digital certificates for the client machine. Employing this wizard greatly reduces the cost and headache of building a streamlined setup process for almost any Access application. And best of all, because the output of the wizard is an MSI file, other commonly used setup editors can make modifications to the package.
The GetAColor UserForm has another twist It remembers the last color that was selected. When the function ends, the three Scrollbar values are stored in the Windows Registry, using this code (appname is a string defined in Modulel) The last argument for the GetSetting function is the default value, which is used if the Registry key is not found. In this case, each color defaults to 128, which produces middle gray. The SaveSetting and GetSetting functions always use this Registry key Figure 15-24 shows the Registry data, displayed with the Windows Regedit.exe program. Figure 15-24 The user's ScrollBar values are stored in the Windows Registry and retrieved the next time the GetAColor function is used. Figure 15-24 The user's ScrollBar values are stored in the Windows Registry and retrieved the next time the GetAColor function is used.
The Microsoft Knowledge Base has an excellent article that describes the sandbox mode as well as expressions that are blocked when the Sandbox is enabled at http support.microsoft.com kb 294698 . The article also describes how to adjust the sandbox mode by changing a setting in the Windows Registry, but note that the Registry key for Access 2007 has changed to
An Access add-in is a library database (an Access database with the extension .mda for Access 97-2003, or .accda for Access 2007) containing the objects and modules needed to support the add-in's functionality, and a special system table called UsysReglnfo with the Registry key information needed to install the add-in. Add-ins are typically stored in the default Microsoft Addlns folder (C Documents and SettingsWser Name Application Data Microsoft AddIns), which was also the default Access add-ins folder for Access 2003). In Access 2007 the default folder for Microsoft's own add-ins is the ACCWIZ folder under the Office folder (on my system, this is E Microsoft Office 2007 Beta Office12 ACCWIZ). However, it is a good idea to keep your own add-ins in the main AddIns folder (C Documents and SettingsWser Name Application Data Microsoft AddIns for Windows XP or C Users User Name AppData Roaming Microsoft AddIns for Windows Vista) rather than mixed in with the ones installed by Office.
The UserChoices array holds the value of each control. This information is stored in the Windows Registry when the user closes the dialog box and is retrieved when the utility is executed again. This is a convenience feature I added because I found that many users tend to perform the same operation every time they use the utility.
This must be a subkey of the HKEY_ CURRENT_USER Software VB and VBA Program Settings registry key. Deletes a complete application key, one of its subkeys, or a single value entry from the Windows registry. section can contain a relative path (similar to that used to describe the folders on a hard drive) to navigate from the application key to the subkey to be deleted. For example, to delete the value entry named TestKey in the registry key HKEY_CURRENT_USER Software VB and VBA Program Settings RegTester BranchOne BranchTwo, you'd use You can't use DeleteSetting to delete entries from registry keys that aren't subkeys of HKEY_CURRENT_USER Software VB and VBA Program Settings. _ Testkey , 10 MsgBox Now look in RegEdit End Sub Never assume that the key you want to delete is necessarily present in the registry. DeleteSetting deletes a user key (that is, a subkey of HKEY_ CURRENT_USER) except on Win95 systems that aren't configured to support multiple users,...
Once you have developed, debugged, and secured your COM Add-in, you can create an installation setup program with either the Setup Wizard, if you are using Visual Basic 5, or the Package and Deployment Wizard if you are using Visual Basic 6. If you use the Visual Basic 5 Setup Wizard, you must add code to the setup program to ensure that the correct registry settings will be created for your Add-in. See Add-In Registration earlier in this chapter for the correct registry key names and values for a COM Add-in. If you use Visual Basic 6 and the Package and Deployment Wizard, all the registration choresare handled for you automatically. The discussion that follows assumes that you will use the Visual Basic 6 Package and Deployment Wizard to package your Add-in.
The RegistryRootKey parameter stores the browser window's size and location in the Windows Registry. This lets your application make the Web browser appear with the same size and location each time it is called. The information is stored in HKEY_CURRENT_USER and so is specific to each user. If you don't want to use this capability, pass a null (empty) string in this parameter.
Profiles are saved and recalled from the Windows Registry. You can save them and export them to .arg files, but they are actually Registry export files, having the same internal content and structure as a Windows .reg file. In fact, you can rename them as .reg files and doubleclick them to import them directly into the registry. AutoCAD, however, provides API access into the Profiles object to allow you to manage profiles from within AutoCAD. The True argument at the end of the ImportProfile method tells AutoCAD to preserve the path information from the .arg file and save this information into the Windows Registry. Also, notice that at the end of the preceding code I set the newly imported profile to be active. You must make your personal profile active for your settings to take effect.
Dim RegKeyRef As Long ' Get the BMP file class. ' Open the Registry key. Use the Registry Editor to discover more about how OLE works. Registry Editor The code begins by using RegOpenKey to open the Registry and get a reference (also called a handle) to a specific Registry key. This function requires the hive key, a subkey (the file extension), and a variable to hold the Registry key reference as arguments. You must include code that checks the key for a 0 return value. This value tells you that the key doesn't exist on the target machine. If the key doesn't exist, you can't open that object on that target machine because it lacks the required support. After the code gets a Registry key reference, it uses it to ask for the program type information by using the RegQueryValue function. To request the information in the (Default) value, you send an empty string as the second argument. Otherwise, you can include a string that has a specific value name...
Oddly, there is no direct way to remove an add-in from the Addlns collection. The Addlns collection does not have a Delete or Remove method. One way to remove an add-in from the Add-Ins dialog box is to edit the Windows Registry database (using regedit.exe). After you do this, the add-in will not appear in the Add-Ins dialog box the next time that you start Excel. Note that this method is not guaranteed to work with all add-in files.
The add-in files that make up the AddIns collection can be stored anywhere. Excel maintains a partial list of these files and their locations in the Windows Registry. For Excel 2003, this list is stored at You can use the Windows Registry Editor (regedit.exe) to view this Registry key. Note that the standard add-ins that are shipped with Excel do not appear in this Registry key. In addition, add-in files stored in the following directory will also appear in the list but will not be listed in the Registry The Windows Registry does not actually get updated until Excel closes normally. Therefore, if Excel ends abnormally (that is, if it crashes), the add-in's name will not get added to the Registry, and the add-in will not be part of the Addlns collection when Excel restarts.
Though the Windows registry was meant to replace INI (initialization) files, they are still in widespread use. One of the strengths of INI files versus the registry is that, because INI files are simple text, they can be easily inspected and modified using a text editor such as Notepad. INI files can also be copied with ease to other computers.
To establish separate security settings for a mixed installation of Outlook 2000 and Outlook 2002 clients, create a folder named Outlook Security Settings for Outlook 2000 users and a folder named Outlook 10 Security Settings for Outlook 2002 users. The folder from which Outlook reads security settings at boot time is determined by a registry key on the client computer.
With the introduction of Windows XP Professional x64 Edition, a separate view was added to the Registry for 32-bit applications to prevent data in 64-bit Registry keys from being overwritten by keys and values installed by 32-bit programs. Program settings for 64-bit programs are still stored in HKEY_LOCAL_MACHINE Software, while settings for 32-bit programs run are now stored in a new key called
A user uses an Active Document container application such as Internet Explorer or Office Binder to directly open a second application's data file. The container application uses the Windows Registry to determine the application associated with the data file's extension and, if the data file's application is an Active Document server, it runs the server application and its data in an Active Document window.
Change the project's name to match the name you want to give your server component application. This choice of name is important, because it is the name that the Windows Registry will use to identify the server component and the name that clients will use when they instantiate objects from the server component with the servername.classname syntax.
By default, the Outlook project template includes a Setup project in your solution. The Setup project is a standard one, and it includes the correct registry keys needed to register a set of Outlook add-ins. Figure 11.26 shows the keys added by the Setup project. Figure 11.26. Registry keys added by the Setup project
A license key to use with the Controls.Add method is the second argument to the Licenses.Add method and must be licensed to you in order for you to use it legally with software that you distribute to end users. A. is incorrect because, while it is possible to find the license key in the Windows Registry, this is a very tedious method compared to using the return value of Licenses.Add when running the application in your design environment. D. is incorrect because you must provide the license key by invoking Licenses.Add on all user machines. See Managing the License for an ActiveX Control.
When your COM component is ready for distribution, you will want it to be permanently listed in the Windows Registry on your development workstation. You will also want the component to be registered on the workstations belonging to users to whom you will distribute the component.
Before we cover the steps required to create a COM Add-in, you should realize that COM Add-ins are exposed in the Office XP Object Model through the COMAddlns collection object and its member COMAddln objects. You can determine which COM Add-ins are available in a given Outlook application session by iterating over the items in the COMAddlns collection object. The COMAddlns collection object is available as a property object of the Outlook Application object. Although theCOMAddlns collection object is available as a property object for each Application object in the Office suite, the COMAddlns collection object is application-specific, meaning that you can obtain the COMAddlns collection only for the Outlook Application object. The COMAddlns collection object supports only two methods, the Update method and the Items method. The Items method lets you access a COMAddln object from the collection by index or by the COMAddln's COM ProglD. The Update method refreshes the COMAddlns...
However if the component in which you're interested has been properly registered in the Windows Registry, you won't ever need to know the name or location of the Object Library. Instead, the Windows Registry will contain information about the component in which you're interested. In that case, all you need to do is refer to the Windows Registry entries for the component, as in the following description. 2. Scroll through the Available References list until you find the name of the COM component that you want (see Figure 10.1). The Object Library list you see here is not a VB-specific feature, but is generated from the Windows Registry.
After you create one of these types of add-ins, you then register the add-in so that your applications can use it. One way to register an add-in is using the Add-in Manager in Access. Another way is to have the setup program register the add-in automatically. Yet another way to register an add-in is directly, using the Windows Registry.
Prior to Windows XP and Windows Server 2003, Regedt32.exe was the preferred 32-bit Registry Editor for Windows NT and 2000. But, of course, nothing is perfect, and Regedt32.exe had limitations for example, it could not import or export Registry entries (.reg) files. Now, under Windows XP, Windows Server 2003, and Windows Vista, Regedt32.exe is a simple wrapper program that runs Regedit.exe. On Windows NT and 2000, you should use Regedt32.exe whereas on Windows XP, Windows Server 2003, and Windows Vista, you can use either Regedt32.exe or RegEdit.exe.
You can use the Regedit.exe program to change anything in the Registry, including information that is critical to your system's operation. In other words, if you change the wrong piece of information, Windows may no longer work properly. Get into the habit of choosing the File Export command in Regedit. This command enables you to save an ASCII version of the Registry or just a specific branch of the Registry. If you find that you messed up something, you can always import the ASCII file to restore the Registry to its previous condition (choose the Registry Import Registry File command). Refer to the Help file for Regedit for details. You can use the Registry Editor program (Regedit.exe, in the Windows folder) to browse the Registry and even edit its contents if you know what you're doing. Before beginning your explorations, take a minute to read the sidebar titled Before You Edit the Registry . . . . Figure 4-8 shows what the Registry Editor looks like. Figure 4-8 The Registry Editor...
Whether you use it to distribute runtimes or just the application, the package wizard can guide you through the process of creating a professional delivery for your solution. The package wizard creates the MSI installer, which installs the entire database solution for the user. Among other things, the wizard allows you to include the database files, icons as well as additional files and folders. It can also be used to create short cuts for the user, to set registry keys and more. And, as in the past, the wizard allows you to save a template of a package solution. So, when you need to make modifications, you don't have to start from scratch. Again, I refer you to Chapter 21.
When Excel starts, it reads its settings from the Windows Registry and opens any add-ins that are installed (that is, those that are checked in the Add-Ins dialog box, which is displayed when you choose Tools Add-Ins). It then displays an empty workbook the number of sheets in the workbook is determined by a user-defined setting that is stored in the Windows Registry. You can change this number by editing the Sheets in the New Workbook setting located in the General tab of the Options dialog box (choose Tools Options). o Causes Excel to register itself in the Windows Registry. It replaces regserver Forces Excel to reregister itself in the Windows Registry and then quit. Use this switch when you want Excel to rewrite all its Registry keys and reassociate itself with Excel files, such as workbooks and charts. Forces Excel to unregister itself in the Windows Registry and then quit.
The Registry key for Word's Automation object and the reference to the Application object in VBA just happen to be the same Word.Application. They do not, however, refer to the same thing. When you declare an object As Word. Application or As New Word.Application, the term refers to the Application object in the Word library. But when you invoke the function CreateObject( Word. Application ), the term refers to the moniker by which the latest version of Word is known in the Windows System Registry. This isn't the case for all Automation objects, although it is true for the main Office 2003 components. If the user replaces Word 2002 with Word 2003, CreateObject( Word.Application ) will continue to work properly, referring to the new application. If Word 2003 is removed, however, CreateObject( Word.Application.11 ), which uses the alternate version-specific moniker for Word 2003, will fail to work.
The Package Wizard is like the extra point after a touchdown. It produces incredibly professional-looking setup routines. Now you can deploy Access solutions with the same panache as Microsoft and all the other big guys. The Package Wizard builds the cabinet file (CAB) that includes Windows Registry Keys and even the digital certificate, if appropriate, that need to be included when deploying an Access solution.
It's important to understand that Excel reads the Windows Registry only once when it starts up. In addition, Excel updates the Registry settings only when Excel closes normally. If Excel crashes (unfortunately, not an uncommon occurrence), the Registry information is not updated. For example, if you change one of Excel's settings, such as the visibility of the status bar, this setting is not written to the Registry until Excel closes by normal Lists add-ins that appear in the list box when you choose the Tools Add-Ins command. Add-ins that are included with Excel do not appear in this list. If you have an add-in entry in this list box that you no longer use, you can remove it by using the Registry Editor. Although you can change most of the settings via Excel's Options dialog box, several other useful settings cannot be changed directly from Excel (but you can use the Registry Editor to make changes).
Figure 14.7 - COM Add-in settings in the Windows Registry Editor. Controlling Initial Load Behavior The following sections describe how you can add Property Pages to the Outlook Tools Options dialog box or the Folder Properties dialog box. Property Pages are discussed in the context of COM Add-in development because Property Pages provide a means of persisting settings for your COM Add-in to the Windows registry. Two module-level variables, gblnDirty and IsLoading, help to ensure that the property page is not marked as dirty when the control is loading. Typically, you would have the values for the constituent controls persist on your Property page in the Windows registry. When the user clicks OK or Apply on the Property page, you save the values represented by the controls on that page to the registry. When the user invokes the Property page by selecting the Outlook Tools Options command, you have to retrieve the values you stored in the registry and set thecontrols on your Property...
Perhaps the most significant new feature of Outlook 2002 is the Outlook E-Mail Security Update. Introduced in response to the damage wrought by e-mail viruses such as Melissa and ILoveYou, the Outlook E-Mail Security Update was offered originally as a patch for Outlook 2000 SR-1 a and Outlook 98. This update is not available for Outlook 97. In Outlook 2000 SP2 and Outlook 2002, the Outlook E-Mail Security Update is built into Outlook. It cannot be removed, and administrative control is available only for users who are connected to an Exchange server. Administrative control is provided by an Administrative form that is located in a folder in the Public Folder hierarchy and by a registry key setting that causes Outlook to read values from the form when Outlook launches.
Windows registry, the Addin Display Name is stored in the Friendly Name key. If the name is to come from a resource file specified in the Satellite DLL Name box on the Advanced page, the name must begin with a number sign ( ), followed by an integer specifying a resource ID within the file. Registry Key For Additional The registry subkey to which additional data is to be written. Addin Data Outlook COM Add-lns are registered in the Windows registry under the following key Each COM Add-in has a subkey under the Addins key based on its ProgID. If you are using Visual Basic 6 to create your Add-in, the ProgID subkey and some essential key values are automatically created for you when you compile your Add-in project or when a user installs a COM Add-in. Figure 14-7 shows the Addins key in the Windows Registry Editor. Registry Editor
Getting Information About a COM Component Developers of potential client applications can find out about your server component by looking at the Windows Registry, or by using utilities such as VB's Object Browser. You can register your server component in the Windows Registry in one of several ways. These ways are discussed in more detail in the section titled Registering and Unregistering a COM Component.
Note If you'd like to take a look at the content of the ReportML file, you must tell Access not to delete it by default. This requires that you add the following entry to the Windows registry Unless you are very familiar with using RegEdit to edit registry settings, do not attempt this task on your own. Once you make the registry setting and complete the export to XML, you can open the ReportML file and look at its contents. This file should have the name of the Access object you exported, followed by an underscore and the word report. For example, if you exported the Shippers table to an XML file, the ReportML name is Shippers_report.xml.
Appendix A addresses the issues and processes of upgrading, converting, and compatibility. The other 12 appendixes provide lists and tables that complement specific chapters in the book. You'll find detailed lists of objects for both DAO and ADO as well as the Access object model and Windows Registry. The appendixes on naming conventions and reserved words provide invaluable information that not only can strengthen your programming style but can save you from using terms or characters that can cause hours of needless pain and frustration in debugging and correcting. The last appendix is filled with tips and tricks to make it easier and faster for you to develop professional applications, all solicited from MVPs and developers around the world.
The initial chapters are written in a tutorial format with detailed examples. True to the Wrox Programmer's Reference standard format, the book includes numerous reference appendixes with details on the various object models you might use when writing VBA code in Access. It also provides a detailed primer on the Windows Registry and a listing of common API functions you might want to use in your code.
On the next screen, you can indicate whether any of the files that you are publishing with the COM component require an entry in the Windows Registry (see Figure 12.19). Usually you need to do nothing on this screen, because VCM is pretty good at guessing which files need registration. In fact, if you try to check a file that obviously doesn't need registration (such as a source-code file), VCM will warn you that the file doesn't need registration and will refuse to check the box next to the file's name. You can indicate the files that belong to a published component and that must be registered in the Windows Registry. You can indicate the files that belong to a published component and that must be registered in the Windows Registry.
When you compile your COM Add-in in Visual Basic 6, you have actually registered the COM Add-in in the correct location in the Windows registry. When you deploy your COM Add-in, the Package and Deployment wizard handles registration automatically on the target installation system. If you are using Visual Basic 5 to create your COM Add-in, you must create registry entries for the COM Add-in programmatically. If you are using Visual Basic 5, a registry key with the ProgID of your COM Add-in and three required subkeys for the COM Add-in must be created in the following location A descriptive string that is not exposed by the COMAddln object. If you need to, you can retrieve this string from the Windows registry.
|RegistryMum Registry Cleaner||www.maxutilities.net|
|Registry Easy Cleaner|
|Pcfixkit Registry Cleaner & PC Optimizer||www.pcfixkit.com|
|WiseFixer Registry Cleaner|
|RegCure Completely clean your windows registry|
|Regserve Registry Cleaner||ww1.regserve.com|
|Registry Kit Registry Cleaner Fix Registry Errors||registrykit.com|
|Registry Toolkit Registry Cleaner Tool|
|PC Booster Optimize Your PC Automatically||www.inklineglobal.com|
PC Repair Tools Official Download Link
If you can not wait, then get PC Repair Tools now. Your Download will be instantly available for you right after your purchase.