Any time you call CreateObject, VBSEdit will load the type library for that COM server, and display the objects/methods/properties/enums in the object browser, as well as the code completion prompts.
If your script is designed to connect to a running instance of DxDesigner, you can trick VBSEdit like this:
If 1 Then
Set vdapp = GetObject(,"Viewdraw.Application")
Set vdapp = CreateObject("Viewdraw.Application")
VBSEdit will load the type library to use while editing the script, but will connect to the running DxDesigner application instead of creating a new instance at runtime.
For best performance, you will want the script to run in the same process as DxDesigner, so you can change the Set vdapp = GetObject to Set vdapp = Application.
Thanks John, exactly what I was looking for.
I found that you can also just put the CreateObject in a comment and VBSEdit will still load the browser data.