There were definitely two nasty bugs in the COM code which I believe that I
have fixed and checked into CVS. But the root cause of your problem is
actually a COM exception thrown by ADODB.Connection. I see this exception
when I pass "position" (a valid field name in the database) in a SQL queries
On Tue, 16 Apr 2002 09:26:35 -0500, you wrote:
>It may be the ADO connection with Access. I am not sure. DB_adodb is a DB
>class I am writing for the Pear_DB abstraction layer.
>
>I am attaching it to this email so everyone can look at it. At this point it is
>kind of a hack. There is no capa
I can only assume this is something you are writing) and
> I
> > will trace into the source and find out what is happening and fix it if
> > there is a bug or tell you what is wrong with your source otherwise.
> >
> > Alan.
> > - Original Message -----
&
ssage -
> From: "Scott Carr" <[EMAIL PROTECTED]>
> To: "PHP Windows" <[EMAIL PROTECTED]>
> Sent: Monday, April 15, 2002 17:43
> Subject: [PHP-WIN] COM and ADODB access
>
>
> > I am having a problem with SQL statements passed to a COM object.
>
I am having a problem with SQL statements passed to a COM object.
"SELECT * FROM Reports" works fine.
"SELECT IDCode, Report_Name, Report_Description, Report_Status FROM Reports"
blows up. I have been having this issue with 4.0.6 through 4.2.0 RC3.
Has anybody else tried to pass semi-long st
