WD2000: GetAllSettings Returns Type Mismatch (212649)
The information in this article applies to:
This article was previously published under Q212649 SYMPTOMS
When you use the Microsoft Visual Basic for Applications GetAllSettings function to return a list of key settings and their respective values, the following error message may appear:
Run-time error '13': Type Mismatch
CAUSE
If the value for "appname" or "section" does not exist in the registry, the Visual Basic Editor returns the "Type Mismatch" error.
WORKAROUNDMicrosoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.
To work around this error, use a Visual Basic for Applications macro similar to the following to verify that registry values exist:
Sub GetAllSettingsExample()
Dim vMySet As Variant
Dim iCount As Integer
' Get registry settings.
vMySet = GetAllSettings(AppName:="MyProjectName", _
Section:="MySection")
' Make sure the variable is not empty.
If Not IsEmpty(vMySet) Then
'Display the Key Names and Values.
For iCount = LBound(vMySet, 1) To UBound(vMySet, 1)
MsgBox vMySet(iCount, 0), vMySet(iCount, 1)
Next
End If
End Sub
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. REFERENCES
For more information about getting help with Visual Basic for Applications, please see the following article in the Microsoft Knowledge Base:
226118 OFF2000: Programming Resources for Visual Basic for Applications
Modification Type: | Major | Last Reviewed: | 6/17/2005 |
---|
Keywords: | kbbug kbdtacode kbmacroexample kbpending KB212649 |
---|
|