Edit report at https://bugs.php.net/bug.php?id=24718&edit=1
ID: 24718
User updated by: wizards567 at gmail dot com
Reported by: wizards567 at gmail dot com
Summary: odbc_result_all crashes on some results
Status: Assigned
Type: Bug
Package: *General Issues
Operating System: Windows 2000 Professional
PHP Version: 4.3.2
Assigned To: kalowsky
Block user comment: N
Private report: N
New Comment:
There's a lot of info. I'll be back again.
Previous Comments:
------------------------------------------------------------------------
[2012-05-18 10:38:42] admte33ch at gmail dot com
There's a wealth of information here. I'll be back again.
------------------------------------------------------------------------
[2012-05-17 11:01:10] lley311ann at gmail dot com
Thank you very much for that big article
------------------------------------------------------------------------
[2004-05-26 02:18:59] johnr at silver-bullet dot co dot nz
I have a very similar problem with an access database (97 I think).
The database is password protected and we need the data to import into a new
system - mdbtools and php works a treat, except on one table.
It will retrieve x records and then crash. Trying to retrieve the next record
(in sequence, after the last successful fetch) also results in a crash.
mdb-export works a treat.
I suspect that long memo fields are the problem. (I haven't checked every one
but all the ones that failed that I did check had long memo fields.)
The schema (as reported by mdb-schema) is:
CREATE TABLE Customer
(
CustID Long Integer (4),
AccCode Text (10),
StatusFlag Integer (2),
SName Text (50),
Initials Text (50),
Title Text (5),
Street Text (50),
Suburb Text (50),
City Text (50),
State Text (30),
Post1 Text (50),
Post2 Text (50),
PostCode Text (20),
TeleH Text (15),
TeleW Text (15),
TeleM Text (15),
FaxNo Text (15),
Email Text (50),
Code Text (4),
CreditLimit Text (20),
Contact Text (50),
ODInterest Boolean,
Preferred Text (50),
Notes Memo/Hyperlink,
SendNotice Integer (2)
);
------------------------------------------------------------------------
[2003-11-05 00:35:12] sni...@php.net
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.
------------------------------------------------------------------------
[2003-10-31 09:55:32] kalow...@php.net
You are correct that a LONGCHAR is not supported,
although I haven't a clue what that would actually be.
A CHAR, VARCHAR, VARBINARY, LONGVARBINARY would all be
valid substitutions though.
Can you try changing that and see if this solves your
problem?
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=24718
--
Edit this bug report at https://bugs.php.net/bug.php?id=24718&edit=1
