SaveSetting & GetSetting Allow Nested Settings

 Last reviewed: February 9, 1996
Article ID: Q145694
The information in this article applies to:
  • Standard, Professional, and Enterprise Editions of Microsoft Visual Basic, 16-bit and 32-bit, for Windows, version 4.0

SUMMARY

It is possible to use the SaveSetting statement to create nested levels of keys and values in the Registry. This behavior is desirable in some cases.

For example, when receiving the location of a SYSTEM.MDA file, the Access engine expects the SystemDB value to exist in a subkey of Engines\Jet, like this:

HKEY_CURRENT_USER 

   \Software
      \VB and VBA Program Settings
         \MyApp
            \Engines
               \Jet
                  SystemDB = c:\access\system.mda
Simply using the syntax for GetSetting supplied in the documentation and online help does not allow for this functionality.

MORE INFORMATION

You can create nested levels in the Registry by using this syntax: 

   SaveSetting "TestApp", "Test2\Test3", "TestVal", "TestSetting"
This will create a section of the Registry that looks like:

HKEY_CURRENT_USER 

   \Software
      \VB and VBA Program Settings
         \TestApp
            \Test2
               \Test3
                  TestVal = TestSetting
This will only work with the 32-bit version of Visual Basic 4.0. If the same line of code is executed with Visual Basic 4.0 16-bit, the result will be a file named TESTAPP.INI, with the following section: 

   [Test2\Test3]
   TestVal=TestSetting
To retrieve values stored in the Registry like this, use the same syntax with the GetSetting function.

Some restrictions are inherited when creating nested keys with SaveSetting.

DeleteSetting and GetAllSettings do not work in the same fashion as they do with non-nested keys.

Additional reference words: 4.00 vb4win vb4all
KBCategory: Kbprg
KBSubcategory: prgother

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: February 9, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.