Assembly: Microsoft.VisualBasic (in microsoft.visualbasic.dll)
public: static Object^ CreateObject ( String^ ProgId, [OptionalAttribute] String^ ServerName )
public static Object CreateObject ( String ProgId, /** @attribute OptionalAttribute() */ String ServerName )
Required. String. The program ID of the object to create.
Optional. String. The name of the network server where the object will be created. If ServerName is an empty string (""), the local computer is used.
Return ValueCreates and returns a reference to a COM object. CreateObject cannot be used to create instances of classes in Visual Basic unless those classes are explicitly exposed as COM components.
For more detailed information, see the Visual Basic topic CreateObject Function (Visual Basic).
To create an instance of a COM component, assign the object returned by CreateObject to an object variable:
Sub CreateADODB() Dim adoApp As Object adoApp = CreateObject("ADODB.Connection") End Sub
The type of object variable you use to store the returned object can affect your application's performance. Declaring an object variable with the As Object clause creates a variable that can contain a reference to any type of object. However, access to the object through that variable is late-bound, that is, the binding occurs when your program runs. There are many reasons you should avoid late binding, including slower application performance.
You can create an object variable that results in early binding—that is, binding when the program is compiled. To do so, add a reference to the type library for your object from the COM tab of the Add Reference dialog box on the Project menu. Then declare the object variable of the specific type of your object. In most cases, it is more efficient to use the Dim statement and a primary interop assembly to create objects than it is to use the CreateObject function.
Interacting with Unmanaged Code
Another issue is that COM objects use unmanaged code — code without the benefit of the common language runtime. There is a fair degree of complexity involved in mixing the managed code of Visual Basic with unmanaged code from COM. When you add a reference to a COM object, Visual Basic searches for a primary interop assembly (PIA) for that library; if it finds one, then it uses it. If it does not find a PIA, then it creates an interoperability assembly that contains local interoperability classes for each class in the COM library. For more information, see COM Interoperability in .NET Framework Applications.
You should generally use strongly bound objects and primary interop assemblies whenever possible. The examples below use the CreateObject function with Microsoft Office objects for demonstration purposes only. However, these objects are easier to use and more reliable when used with the appropriate primary interop assembly.
Creating an Object on a Remote Computer
You can create an object on a remote networked computer by passing the name of the computer to the ServerName argument of the CreateObject function. That name is the same as the Machine Name portion of a share name: for a share named "\\MyServer\Public," ServerName is "MyServer."
Refer to COM documentation (see Microsoft Developer Network) for additional information on making an application accessible on a remote networked computer. You may need to add a registry key for your application.
The following code returns the version number of an instance of Excel running on a remote computer named MyServer:
Sub CreateRemoteExcelObj() Dim xlApp As Object ' Replace string "\\MyServer" with name of the remote computer. xlApp = CreateObject("Excel.Application", "\\MyServer") MsgBox(xlApp.Version) End Sub
If the remote server name is incorrect, or if it is unavailable, a run-time error occurs.
Use CreateObject when there is no current instance of the object. If an instance of the object is already running, a new instance is started, and an object of the specified type is created. To use the current instance, or to start the application and have it load a file, use the GetObject function. If an object has registered itself as a single-instance object, only one instance of the object is created, no matter how many times CreateObject is executed.
Creating Framework Objects
You can use the CreateObject function only to create a COM object. While there is no exact equivalent mechanism for creating a .NET Framework object, the Activator in the System namespace contains methods to create local or remote objects. In particular, the CreateInstance method or the CreateInstanceFrom method might be useful.
The following example uses the CreateObject function to create a Microsoft Excel worksheet and saves the worksheet to a file. To use this example, Excel must be installed on the computer where this program runs. Also, you must add a reference to the type library from the COM tab of the Add Reference dialog box on the Project menu. The name of the type library varies depending on the version of Excel installed on your computer. For example, the type library for Microsoft Excel 2002 is named Microsoft Excel 10.0 Object Library.
Sub TestExcel() Dim xlApp As Microsoft.Office.Interop.Excel.Application Dim xlBook As Microsoft.Office.Interop.Excel.Workbook Dim xlSheet As Microsoft.Office.Interop.Excel.Worksheet xlApp = CType(CreateObject("Excel.Application"), _ Microsoft.Office.Interop.Excel.Application) xlBook = CType(xlApp.Workbooks.Add, _ Microsoft.Office.Interop.Excel.Workbook) xlSheet = CType(xlBook.Worksheets(1), _ Microsoft.Office.Interop.Excel.Worksheet) ' The following statement puts text in the second row of the sheet. xlSheet.Cells(2, 2) = "This is column B row 2" ' The following statement shows the sheet. xlSheet.Application.Visible = True ' The following statement saves the sheet to the C:\Test.xls directory. xlSheet.SaveAs("C:\Test.xls") ' Optionally, you can call xlApp.Quit to close the workbook. End Sub
Windows 98, Windows 2000 SP4, Windows CE, Windows Millennium Edition, Windows Mobile for Pocket PC, Windows Mobile for Smartphone, Windows Server 2003, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP SP2, Windows XP Starter Edition
The .NET Framework does not support all versions of every platform. For a list of the supported versions, see System Requirements.
Other ResourcesCreateObject Function (Visual Basic)
GetObject Function (Visual Basic)
Dim Statement (Visual Basic)
COM Interoperability in .NET Framework Applications
Interoperating with Unmanaged Code