NCS Logo - Click for home page Northstar Developer Center
Platforms
All Platforms
.NET Framework (1.x - 4.x)
Active Server Pages
ASP.NET
C#
SQL Server
VB.NET
Visual Basic

Keywords
.NET Data Types
.NET E-mail
.NET Events
.NET Functions
.NET Object Programming
.NET System.Configuration
.NET System.Diagnostics
.NET System.IO
.NET System.Net
.NET System.Net.Sockets
Active Data Objects
ASP Architecture
ASP Black Belt
ASP Built-in Functions
ASP Built-in Objects
ASP Debugging
ASP Performance
ASP Security
ASP Syntax
ASP.NET Authentication
ASP.NET Controls
ASP.NET Data Access
ASP.NET Features
ASP.NET Master Pages
ASP.NET Page Events
ASP.NET Security
ASP.NET ViewState
Atom
Certifications
COM, DCOM, COM+
Data Access
E-Mail
Errors
Exporting Data
HTML Tips
IIS
Object-Oriented Programming
RSS
SQL
Uncategorized ASP Tips
VB API Programming
VB Forms
VB Syntax
XML

Book Support
Visual Basic 6 Bible
ASP Bible
ASP Weekend Crash Course
ASP.NET At Work
Creating Web Services

Passing Objects to COM Components from VBScript

Written by Eric Smith, Northstar Computer Systems LLC

Using COM components; that is, ActiveX DLLs created in a language like Visual Basic, can really speed up processing on your ASP application. If you ever need to pass an object to a public method (property, subroutine, or function), use a data type of Variant within the COM component. Here's an example of a method that accepts an ADO Connection object and then stores it in a local object variable for later use:
Option Explicit
Private m_dcnDB As ADODB.Connection

…

Public Sub DoSomething(dcnDB As Variant)
   Set m_dcnDB = dcnDB
   …
End Sub
The reason you have to do this is that VBScript has no object data type -- everything's a variant. If you don't do this, you may get Type Mismatch errors for the object you're trying to pass in. Note that any object parameter is subject to this problem -- not just ADO objects.

Keywords: [ Uncategorized ASP Tips ]

Publication Date: 7/1/1999