Chilkat HOME Android™ Classic ASP C C++ C# C# UWP/WinRT DataFlex Delphi ActiveX Delphi DLL Visual FoxPro Java Lianja MFC Objective-C Perl PHP ActiveX PHP Extension PowerBuilder PowerShell PureBasic Python Ruby SQL Server Swift Tcl Unicode C Unicode C++ Visual Basic 6.0 VB.NET VB.NET UWP/WinRT VBScript Xojo Plugin Node.js
Chilkat Visual Basic Examples
Using ActiveX Components in Visual Basic 6.0
To use an ActiveX component in VB 6.0, you must first add a reference to the component from within your VB6 project.
To add a "Reference", select Project --> References... from the VB6 IDE and check the checkbox for the component to be referenced, as shown below:
Then select the component to be referenced:
Creating the ActiveX Component Dynamically at Runtime
To instantiate a new instance of an ActiveX component, use the "New" keyword, as shown in the code fragment below:
' Dim as New: Dim ftp As New ChilkatFtp2 ' Alternatively, Dim and instantiate later: Dim x as ChilkatFtp2 Set x = New ChilkatFtp2
Dim an ActiveX Component with Events
If your applications intends to process event callbacks fired by an ActiveX, the component must be declared "WithEvents", as shown below:
' Note: The WithEvents can only appear in the declaration ' section of a module, and cannot be local to a procedure. ' Also, it cannot be used with the "New" keyword. ' The object creation must occur in a separate step, typically ' in the Form load. Dim WithEvents ftp As ChilkatFtp2 Private Sub Form_Load() Set ftp = New ChilkatFtp2 End Sub
Adding an ActiveX Event Callback Function in Visual Basic 6.0
Wiring the ActiveX for events is easy. First, display the "Code View" in the VB6 IDE and select the object you previously declared "WithEvents", as shown below:
Next, select the event:
Visual Basic will automatically generate the event procedure for you. Here are a few event procedures VB6 generated for the Chilkat FTP2 ActiveX:
Private Sub ftp_AbortCheck(abort As Long) End Sub Private Sub ftp_PutProgress(ByVal pctDone As Long) End Sub
Notice that the procedure names follow a pattern: VARNAME_EVENTNAME. This is important. If the name of the procedure is not correct, it will not be called.
© 2000-2013 Chilkat Software, Inc. All Rights Reserved.