XL5: Network Admin Method for Updating Registration Database

Last reviewed: September 12, 1996
Article ID: Q129422
The information in this article applies to:
  • Microsoft Excel for Windows, versions 5.0, 5.0c

SUMMARY

If you are a network administrator, you may want use a batch method to update users' REG.DAT files. For example, you may want to do this if you want all network users to move their object library (.OLB) files to their local workstations.

For information about a situation in which you would want to use this method, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q120404
   TITLE     : XL5: "File Not Found" Error Using References Dialog Box

MORE INFORMATION

To have users update references in the Windows registration database file, REG.DAT, use the steps below to create a .REG file.

Creating a .REG File

To correct this type of problem for many workstations, you can create and distribute a .REG file to the users that have the problem. The users can double-click the .REG file in Windows File Manager to automatically update the REG.DAT entry. A .REG file that you create must follow certain requirements in order to update the REG.DAT file correctly:

  • The file be in ASCII text.
  • The word REGEDIT must be the only word on the first line of the file.
  • The additional lines of the file include a "path" to the key to be updated and a value for that key.

Example .REG file

Microsoft does not support customer modifications to the REG.DAT file. You should use caution when you make changes to the Windows registration database. Always make a backup copy of the REG.DAT file before you change it. Microsoft provides this example for illustration only, without warranty either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose. This example is provided "as is" and Microsoft in no way guaranties that the following information can be used in all situations.

The following is an example of a file that can be used to update the entries for the XLEN50.OLB file and the VBAEN.OLB file discussed above.

  1. In a text editor, such as Notepad, enter the following text in a new file.

          REGEDIT
    

          HKEY_CLASSES_ROOT\TypeLib\{00020813-0000-0000-C000-
          000000000046}\1.0\9\win16 = C:\EXCEL\XLEN50.OLB
    

          HKEY_CLASSES_ROOT\TypeLib\{000204F3-0000-0000-C000-
          000000000046}\1.0\9\win16 = C:\WINDOWS\SYSTEM\VBAEN.OLB
    

    Note that in the above example, the directories C:\EXCEL and C:\WINDOWS must be the Microsoft Excel directory and the Microsoft Windows directory respectively on the users workstation.

  2. Save the file as CORRECT.REG. (Note that you can give this file any valid MS-DOS filename. However, in order for the file to be associated with the registration database by default, you should give the file the extension .REG).

  3. Distribute the file to the users who are experiencing this problem.

  4. To correct the problem, the user must double-click the .REG file in File Manager to merge this information into the Registration Database file on their computer.

NOTES:

   The formatting of this article may force the example entries above to
   wrap to the following line. All entries in the .REG file must be entered
   on a single line. In the above example, a blank line is inserted between
   each entry.

   There are 10 zeros in the above numeric sequence "000000000046". Failure
   to enter this information EXACTLY as shown above will result in the
   creation of a NEW ENTRY in your REG.DAT file, and the desired result
   will not be achieved. (It is most likely that no error message will be
   given, and no adverse effects will occur.)

   There should be a carriage return character at the end of every line of
   text.


KBCategory: kbnetwork kberrmsg kbenv
KBSubcategory: xlwin

Additional reference words: 5.00 5.00c reg dat vbaen xlen50 novell vlm .vlm
banyan vines vine ghost drive



THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 12, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.