RE: Does Informix OLEDB support OpenSchema?

Help, I did tried and got this run-time error '3251': Object or provider is not capable of performing requested operation. Did I missed to load some components/refrence objects? How I may going to fix this? Please help. Thankx, Roger Lacson -----Original Message----- From: owner-informix-list@iiug.org [mailto:owner-informix-list@iiug.org]On Behalf Of Shawn Moe Sent: Wednesday, June 04, 2003 4:48 PM To: informix-list@iiug.org Subject: Re: Does Informix OLEDB support OpenSchema? Hi, It looks like the connection string is not correct for a connection using the Informix OLEDB provider. There are some changes required when switching between the OLEDB provider and the OLEDB bridge for ODBC. The user should be mentioned as "User Id = username" and the data source should be mentioned as "Data Source = dbname@servername". With a correct connection string, we are able to see the desired result, i.e the list of tables in the current database. Here is the code we used to verify. Private Sub Command1_Click() Dim cCmd As New ADODB.Command Dim rsRow As New ADODB.Recordset Dim cn As New ADODB.Connection Dim connectstring As String connectstring = "Provider=Ifxoledbc; Data Source=common_db@foo9405; user id=informix;password=abc" cn.Open (connectstring) Set rsRow = cn.OpenSchema(adSchemaTables) rsRow.MoveFirst While (Not rsRow.EOF) MsgBox rsRow.Fields(0) + " " + rsRow.Fields(1) + " " + rsRow.Fields(2) + " " + rsRow.Fields(3) rsRow.MoveNext Wend End Sub Regards, Shawn Moe msilberb@baan.com (malky) wrote in message news:<86d37283.0306040232.4210dec7@posting.google.com>... > hi, > > here is code example: > > Dim conn As New ADODB.Connection > Dim rs As New ADODB.Recordset > > conn.Open "Provider=ifxoledbc;Data Source=my_db;User=informix;Password=informix" > Set rs = conn.OpenSchema(adSchemaTables) > > connection opens successfully, but on OpenSchema i'm getting: > ADODB.Connection error number 3251: > "Object or provider is not capable of performing requested operation." > > NOTE: schema opens successfully if i use ODBC. it is only OLEDB problem. > > is it a known limitation, or there *is* a solution? > > thanks a lot, malky