Database Search
If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.
TechHome
OLE COM ADO CDO ADSI LDAP
 | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
|
- !! A List of Links to various OLE docs !!
- !! Understanding COM !!
- 1129 ObjectCreate
- 1129 OleInitiate Failed UAC
- 1129 OleInitiate Failed
- 1251 Ole - WIL Ole interface Dll not found
- Access to Excel Converter
- Access2000 Transaction Processing Demo
- Add Application to the Windows Firewall Exceptions List
- ADO vs ODBC
- ADO vs OLEDB vs ODBC
- Automatic Update from MicroSoft
- Bring up the RUN Dialog
- BYREF return parameters
- Close All Open OLE COM Objects
- Close an Object
- Closing Objects Explained
- Code to Create a Temporary DB
- Collaboration Data Objects Roadmap
- COM Constants for MS Office Applications
- COM Interfaces Explained
- COM Widestring Value Issue
- CommandTimeOut - lesson learned
- Connection String
- Convert Data Returned OLE
- Converting Pre 2004B OLE Scripts
- Copy Table Structure With SQL
- Create Object
- Create Recordset in Memory
- CreateObject Remote Computer
- Database ISAM Example
- dBase IV Creation
- Delete Mailbox in Exchange
- Determining if a Particular Update has Been Installed
- Determining Whether Automatic Updates is Enabled
- Display the Windows Run Dialog Box
- Does WinBatch Support 3rd party COM objects
- DSO Tabular Paging Demo
- Enumerate Citrix Applications
- Find Object Name and Properties
- Find User on Workstation
- ForEach Problem
- Generate GUIDs using ObjectType
- Get Audio File Information
- Get Information for IOMega Zip Drive
- Get Number of Records in Each Table
- Getting Multivalued Properties and Arrays
- GUID Create
- Handle Reassignment
- How to include an Office Assistant
- Insert Data into an SQL Server 2000
- Install CAPICOM on Win7
- Intcontrol 71 and Number of OLE Channels
- Interacting with Citrix
- IPCONFIG Results From STDOUT
- IsObject UDF
- List Components in Com Catalog
- List Databases on a Server
- List OLE DB Providers
- Load Data from ASCII File to a Java Applet Window
- MatLab COM Automation
- Method with Variant Parameters Explained
- Multi-Dimensional SafeArrays are NOT supported
- Named Parameters
- Object 101
- ObjectCreate Cannot Access Remote Server
- ObjectEventAdd Issue
- Office 2007 Driver Tips
- OLE COM Default Member Discussion
- OLE Explanation
- OLE Failing unless IE4 Installed - DCOM98
- OLE Property and Method Name Limit
- OLE Shell functions
- OLE2 Automation Tips
- Open DB and Permit Working with Tables
- Oracle Objects
- Pass ByRef Type Parameter
- Passing an Array as a Parameter to an OLE Method
- Passing Parameters
- Primer - Fabricated Hierarchical Recordsets
- Problems Writting a VB to WinBatch OLE Code Converter
- Read and Write to a Parallel Port
- RecordSets to HTML - with some Javascript
- Regular Expressions with WB
- Remotely Stop or Start COM Components
- Sample Code to Query a MIMSXServer
- Save Binary Streams to DB
- Set Proxy Server and Port
- Setting Group Policy Objects
- Shell ExtendedProperty
- Shell Helper Object
- SQL Server Update Stored Procedure
- Textract Problem
- textract test
- TextStream and Scripting.FileSystemObject
- Translate VB Default Member Name
- Trapping COM OLE Errors
- UDF to Return an Array of DB Table Types
- Un supported Variant Type Error With Concatenation
- Unicode Conversions with FileSystemObject
- Using the Object Browser
- Using the Visual Basic Object Browser
- Vbscript Array in WIL
- Virtual Server COM CoInitializeSecurity
- VT_DECIMAL Versus FLOAT
- WinBatch and Dot NET
- WinBatch Equivalent To VB Nothing
- WinBatch OnError
- Windows Firewall
- Windows Image Acquisition
- Working with Office Applications
- Write-Read DBF
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
COM Interfaces Explained
Keywords: Late Early Bind Interface iDispatch Dispatch IUnknown ObjectGet ObjectCreate
IUnknown Interface is by definition the base interface of all COM interfaces. WinBatch can only access an "late bind" interface. The late-binding COM interface is based on the IDispatch interface and is what you are using when you use the WinBatch COM and dotNet subsystem. Microsoft intended the IDispatch interface for use by scripting languages like WinBatch. WinBatch is unable to access "early bind" interface in that it is primarily intended for use in native C++. MSFT did this by design and the result is evidenced by the fact that the interface pointers are arranged in memory exactly the same way that pointers to C++ object members are arranged in memory. To make things even more interesting many COM interfaces have both an early bind interface and a late bind interface through IDispatch so that can be used by both scripting and non scripting languages. Of course, the above barely scratches the surface and doesn't even begin to cover things like in-process and out-of-process servers or the COM client/server threading model. In short, WinBatch only makes use of many early bind interfaces internally and in extenders but does not provide a mechanism for accessing them from scripts other than through their late bind interfaces via the WinBatch COM subsystem. This is primarily because it is an interpreted scripting language and not a 'native' or 'managed' language.
Article ID: W18017
Filename: COM Interfaces Explained .txt
File Created: 2013:09:26:13:56:40
Last Updated: 2013:09:26:13:56:40