bc functions stay odbc_*, rather than to start
> iterating through odbc2...odbc3 and so forth. Don't know an easy
> solution right now.
> Shane
Shane, I agree that the naming convention should stay the same. I'm only
calling it that now so I can test it and reference it with oth
st sense and be the easiest
to support on our end of things.
>-------<
Dan Kalowsky"I'll walk a thousand miles just
http://www.deadmime.org/~dankto slip this skin."
[EMAIL PROTECTED]-
r something
like that, to allow me to keep it in a different release schedule (as ODBC
standards don't change that rapidly). But I've heard some complaints
against such ideas, so I haven't pushed it (yet). Anyways naming
convention can be changed very easily.
>-----
cause of this, I would like to hear back
commentary back on any suggested recourse from those who've done this
already.
Hopefully this will prove to be a useful change, and people will be happy
:) As always send your comments to me.
>------
rt would be good.
The mailing list archives and cvs logs are a good source. The php
documentation is fairly upto date as well.
--
Dan Kalowsky "Tonight I think I'll walk alone,
Worldgate Communications I'll find my soul as I go home."
Software Engi
xecute stat1";
$stmt1 = odbc_execute($stmt1,array(1,"This","Fails"));
}
$stmt2 = odbc_prepare($conn,"INSERT INTO odbctest2
(id,firstname,lastname) VALUES (?,?,?)");
if ($stmt2) {
print "Trying execute stat2";
$stmt2 = odbc_execute($
prepare($conn,"INSERT INTO odbctest2
(id,firstname,lastname) VALUES (?,?,?)");
if ($stmt2) {
print "Trying execute stat2";
$stmt1 = odbc_execute($stmt1,array("1","This","Works"));
}
?>
--
Dan Kalowsky
This was a problem on the 4.0.4 release
(forgot a line break), but I believe the patch made it into the
4.04.pl1.
If you can, please try the latest snapshot from CVS and see if this
problem still exists for you. I was under the impression that much of
this has been fixed for linux as well (I'
