Visual Basic Q&A

Symptoms
When you instantiate a COM component in an out-of-process server (.exe)from Active Server Pages (ASP), another instance of the .exe starts.
Resolution
The default Identity of a COM component in an .exe is the Launching User.The implication of this is that when the Active Server Pages page tries tocreate an instance of this object, it is doing so in the security contextof the anonymous user (IUSR_<machine name>). If this is a different userfrom the user that started the instance of the .exe that is currentlyrunning, another instance of the .exe starts.

Symptoms
When you instantiate a COM component in an out-of-process server (.exe)from Active Server Pages (ASP), another instance of the .exe starts.
Resolution
The default Identity of a COM component in an .exe is the Launching User.The implication of this is that when the Active Server Pages page tries tocreate an instance of this object, it is doing so in the security contextof the anonymous user (IUSR_<machine name>). If this is a different userfrom the user that started the instance of the .exe that is currentlyrunning, another instance of the .exe starts.

Symptoms
An EXE file is not created even though no errors are produced aftercompiling a Visual Basic application that includes a resource file.
Resolution
This will occur when including a resource file which contains a “Version”resource.

Symptoms
A private UserControl loses it Data Bindings when compiled to an EXE.
Resolution
Close the form containing the UserControl before making the EXE.

Symptoms
When you start Visual Basic 6.0 under a new user account or after a new install, and you try to run the Visual Basic 6.0 executable file (VB6.exe), you get the following error message:

Visual Basic was not able to start up due to invalid system configuration. Missing or not registered VB6tmpl.tlb.You are unable to continue and Visual Basic shuts down.
Resolution
The main Visual Basic type library is either missing or mis-registered for the current user. This message reflects the original working name of this file but in released versions of Visual Basic this file was renamed VB6.olb and is located in the same directory as the Visual Basic 6.0 executable (VB6.exe).
The registry should contain a path to this file under the following key:
HKEY_CLASSES_ROOT\TypeLib\{FCFB3D2E-A0FA-1068-A738-08002B3371B5}\6.0\9\win32If the key is missing or pointing to a location where the file cannot be found, Visual Basic returns the preceding error message during startup.

Symptoms
When using the Distributed Component Object Model (DCOM) ConfigurationUtility (Dcomcnfg.exe), only one class for each ActiveX server appears inthe list of applications. This occurs even though an ActiveX server maycontain several classes, each of which is functioning correctly.
Resolution
DCOM provides server level security. All objects within a server share thesame security settings. Therefore, Dcomcnfg.exe only lists the first object(class) for each ActiveX server registered.