Skip to main content

Purpose of Idispatch interface ...

In yesterday's post (About IUNKnown interface ...), I discussed about Adodb.Recordset object creation, in which I invoked 2 methods namely Open and Close correct? when I call these 2 functions what is the background process going on is what I am going to address now.

When a function or a property of an object is called, the background execution is been carried out by an interface called Idispatch interface. It consists of 4 functions names:

1. GetTypeInfoCount: This determines whether the function or property is having any parameter or not.

2. GetTypeInfo: This not only determines the function names but a detailed collection of what are the parameters passed and what are its datatype and what is its return value, whether it is an IN parameter or OUT parameter etc.,

3. GetIDSofName: This determines the unique id given for each function or property of an object. The ID associated with each and every function or property of an object is called Idispatch ID.

4. Invoke: This is the one which does the job. This collects all the information acquired namely the number of parameters, its datatype and then identifies the function based on its ID and execute the function to return the result.

Let me now switch to the example discussed in the yesterday's post. I was calling OPEN method in that, now what happens is

A. First GetIdsofName will fire accepting the OPEN keyword as its parameter and it retreives the corresponding ID of OPEN method.

B. Then, GetTypeInfoCount will determine whether there are any parameters for this OPEN method.

C. Then, GetTypeInfo will collect all the parameters required for the OPEN method, namely the Query, Connection string, Lock, cursor type etc.,

D. Now the invoke method will execute the functionality with all its relevant collected values.

Thats it :) This is what happening internally when we call a method or a function.

Comments

Popular posts from this blog

Registry manipulation from SQL

Registry Manupulation from SQL Server is pretty easy. There are 4 extended stored procedure in SQL Server 2000 for the purpose of manupulating the server registry. They are: 1) xp_regwrite 2) xp_regread 3) xp_regdeletekey 4) xp_regdeletevalue Let us see each one of them in detail! About xp_regwrite This extended stored procedure helps us to create data item in the (server’s) registry and we could also create a new key. Usage: We must specify the root key with the @rootkey parameter and an individual key with the @key parameter. Please note that if the key doesn’t exist (without any warnnig) it would be created in the registry. The @value_name parameter designates the data item and the @type the type of the data item. Valid data item types include REG_SZ and REG_DWORD . The last parameter is the @value parameter, which assigns a value to the data item. Let us now see an example which would add a new key called " TestKey ", and a new data item under it called TestKeyValue :

Screen scraping using XmlHttp and Vbscript ...

I wrote a small program for screen scraping any sites using XmlHttp object and VBScript. I know I haven't done any rocket science :) still I thought of sharing the code with you all. XmlHttp -- E x tensible M arkup L anguage H ypertext T ransfer P rotocol An advantage is that - the XmlHttp object queries the server and retrieve the latest information without reloading the page. Source code: < html > < head > < script language ="vbscript"> Dim objXmlHttp Set objXmlHttp = CreateObject("Msxml2.XMLHttp") Function ScreenScrapping() URL == "UR site URL comes here" objXmlHttp.Open "POST", url, False objXmlHttp.onreadystatechange = getref("HandleStateChange") objXmlHttp.Send End Function Function HandleStateChange() If (ObjXmlHttp.readyState = 4) Then msgbox "Screenscrapping completed .." divShowContent.innerHtml = objXmlHttp.responseText End If End Function </ script > < head > < body > &l

Script table as - ALTER TO is greyed out - SQL SERVER

One of my office colleague recently asked me why we are not able to generate ALTER Table script from SSMS. If we right click on the table and choose "Script Table As"  ALTER To option would be disabled or Greyed out. Is it a bug? No it isn't a bug. ALTER To is there to be used for generating modified script of Stored Procedure, Functions, Views, Triggers etc., and NOT for Tables. For generating ALTER Table script there is an work around. Right click on the table, choose "Modify" and enter into the design mode. Make what ever changes you want to make and WITHOUT saving it right click anywhere on the top half of the window (above Column properties) and choose "Generate Change Script". Please be advised that SQL Server would drop actually create a new table with modifications, move the data from the old table into it and then drop the old table. Sounds simple but assume you have a very large table for which you want to do this! Then it woul