Hi Himanshu, If you're just using Cach� as a relational database then ADO.NET/ODBC will be the simplest way to go. The ActiveX (COM) interface becomes useful if you are using the OO features of Cach�, like instantiating objects, calling their methods and looking at their properties. An instance of an object roughly equates to a row in the table, and the columns become properties.
The ActiveX Interface is well documented (click on Reference Material), though the sample code is all in VB6. I've worked with it in VB.NET, and I can't see any reason why it wouldn't work in C#. Being ActiveX the interface uses COM Interop, which adds a layer of inefficiency. Briefly, the way you work with the ActiveX interface is: 1. Instantiate the Factory and connect it to Cach� 2. Use the Factory's New, Open, OpenID or Static (for classmethods only) methods to create an Object from a Cach� class (.NET datatype is Object). 3. Call that object's methods or access its properties just like a .NET object. Unfortunately it's all late-bound so you get no intellisense at design time. HTH Regards Jay Ayliff Stalis Ltd "Himanshu" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Hi, > > I've just started using Cache from Visual Studio 2003 .NET and found two > ways > - Using COM/ActiveX > - Using ADO .NET > > Is using one or the other better? Using COM/ActiveX method..... I still had > to use factory.DynamicSQL to run the query. > > And in ADO. NET I would be using an SQL query too. > > So just how does one make use of the 'Object' features using COM/ActiveX? Is > there some other way of retrieving data from tables other than > factory.DynamicSQL? > Or do I have to use ADO .NET to get objects? > > Sorry but I was getting a bit lost in that part. > > Thanks in advance > > Regards, > > Himanshu > > P.S. I'm using C# during all this > >
