Re: Windows to Windows ODBC--Openlink fails with PHP alone
| From: | phobo | Date: | Thu, 02 Nov 2000 02:02:56 +0000 |
| Subject: | Re: Windows to Windows ODBC--Openlink fails with PHP alone | ||
| References: | 1 | Groups: | php.db php.windows |
| Request: | Send a blank email to php-db+get-4114@lists.php.net to get a copy of this message | ||
Frank, I tried changing * to actual Fieldnames, all produced same "Driver
not capable" error. I looked on php.net bugs site and openlink development
site; there seems be "unresolved issues" with Openlink/Access/PHP4 -- which
isn't helpful, now is it ...
I thought about trying other queries; both INSERT and DELETE fail, as well.
If I prepare and execute
DELETE FROM WELLGIRLS WHERE RECORD_NR='5'
I get:
Warning: SQL error: [OpenLink][ODBC][Microsoft][ODBC Microsoft Access
Driver] Data type mismatch in criteria expression., SQL state S1000 in
SQLExecDirect in c:\inetpub\wwwroot\phptestbed\Eyede\Admin\iodbc.php on line
18"
---- which IS what I expect. I now know the driver is atleast performing
datatype checking.
But if I fix it by taking the quotes away (DELETE FROM WELLGIRLS WHERE
RECORD_NR=5), I get a warning, which also fails:
Warning: No tuples available at this result index in
c:\inetpub\wwwroot\phptestbed\Eyede\Admin\iodbc.php on line 21
Arg! Any other ideas?
Siggy
PS: The Openlink Driver (which allows linux->win odbc connections), that I
am using is at www.openlinksw.com . I'm using their most recent (stable)
release, Version 2.7B (Release 3.2) Tue Jan 18 2000 (cvsid 00050).
More importantly (?), the MS Access Driver I am using is 4.00.4403.02
(8/12/1999), using ODBCJT32.dll -- on Windows 2000 :)
----- Original Message -----
From: "Frank M. Kromann" <fmk@swwwing.com>
To: "Sigurd Magnusson" <phobo@paradise.net.nz>
Cc: <php-windows@lists.php.net>
Sent: Thursday, November 02, 2000 2:39 PM
Subject: Re: [PHP-WIN] Windows to Windows ODBC--Openlink fails with PHP
alone
> Hi Sigurd,
>
> I dont know the driver you are using, but the error you are getting tels
me that your driver does not support what you are trying to do. Finding what
the problem is could be done by using a simple SQL statement like
>
> SELECT COLUMN1 FROM TABLE1
>
> Using select * from table1 will select all columns and the error could be
associated with the OpenLink driver beeing incompatible with Access column
types. Try the slect on integer and varchar columns and go through every
type you have in yor table.
>
> - Frank
> >I started working on an ODBC PHP project which connected directly to an
> >Access *shudder* DSN. When I went to implement it, i needed to use
Openlink
> >because the PHP scripts / webserver are to be on a Linux machine.
> >
> >So, all I did was change the DSN name from the Access to the Openlink
DSN;
> >the database I was connecting to is exactly the same. However, it dies.
> >
> >I get lots of fun toys:
> >
> >Warning: SQL error: [OpenLink][ODBC][Driver]Driver not capable, SQL state
> >S1C00 in SQLExecDirect in
> >c:\inetpub\wwwroot\phptestbed\Eyede\Admin\odbctest.php on line 14
> >
> >...
> >
> >The SQL is very simple: SELECT * FROM $db_tablename
> >
> >I'm not sure how to rectify this.
> >
> >I can use a benchmarking program to connect to the ODBC dsn and view all
the
> >rows fine. The Openlink software comes with a program to test the DSN, it
> >views my tables and data perfectly (and quickly too...wooo).
> >
> >SO something is botched with the way PHP is connecting to the DSN. My
> >feeling is that it could be something different in the odbc_connect()
line;
> >but I'm not sure exactly -what- .
> >
> >I'm using
> >IIS5,
> >PHP 4.0.1sp1,
> >Access 2000,
> >Openlink (Request Broker Version 2.7B (Release 3.2))
> >Windows 2000 (5.00.2195)
> >
> >Siggy