Hi Shridhar -
LabView is an Active X container, like Visual Basic, and in a similar manner does not dictate what functionality a Control allows users to access - this is not the Container's role in the architecture!!! Whoever created the database Active X control that you are using decided to export methods for accessing a Recordset, it is their design decision how to let the user to do this. All Active X clients will access the same properties and values with the same methods (even in different environments) - this is what makes ActiveX work!!
Can you access this control in another ActiveX container with methods/properties that are not available in LabView? I do not think so. If so, (I am not sure how this would happen), please describe more - I would be interest
ed in what is going on. Is their a supplemental dll or other code module that goes along with the control? These could be interface specific, but I have never seen this arrangment, it defeats the purpose of ActiveX.
Also, what database are you using and where did this control come from? Who makes this control?
good luck-
Ben Schulte
National Instruments