> Code inspection suggests changing this line of code:

`Error.Raise`

to this:

`Error$.Raise`

Applying the fix causes a compile error.

Version 2.2.0.4138
OS: Microsoft Windows NT 6.1.7601 Service Pack 1, x64
Host Product: Microsoft Office 2016 x86
Host Version: 16.0.4756.1000
Host Executable: EXCEL.EXE

> How was `Error.Raise` not broken in the first place?

This is legal:

Debug.Print Error(13)

Quickfix works:

Debug.Print Error$(13)

Is `Error` the `VBA.Conversion.Error` string-function? If so, it does not return an `ErrObject`; `Error.Raise` throws an "object required" error.

> After a second look, I see that my code is a typo. I meant to type `Err.Raise` (along with the required parameters) but instead typed `Error.Raise`. `Error` is never declared but the code still compiles. Running the code throws run-time error 424 (object required).

Here's the complete code in a new project:

```
Option Explicit
Sub test()
Error.Raise
End Sub
```

When I apply the fix suggested suggested by RD it changes to:

```
Option Explicit
Sub test()
Error$.Rais

> `Error` in `Error.Raise 13` *does* resolve to `VBA.Conversion.Error`, which is what caused the inspection result.

...except if you Shift+F2 on `Error` in `Error.Raise 13`, the VBE itself brings up the object browser... to the `VBA.Conversion.Error` function.

RD is resolving the function call as per specifications... however broken that is.

Hey do you mind me asking a stupid question: In vb.net or c# how can you read this subkey
Computer\HKEY_CLASSES_ROOT\CLSID\{DD2533E5-1513-40D8-82B4-927790D0A895}\InprocServer32

Vogel was saying to try this:
Dim regKey As RegistryKey = Registry.ClassesRoot.OpenSubKey("CLSID\{DD2533E5-1513-40D8-82B‌​4-927790D0A895}\InprocServer32")