Bug #17563 Updated: PHP has encountered an Access Violation at 77FCB2A7
| From: | mfischer@php.net | Date: | Sat, 08 Jun 2002 09:05:19 +0000 |
| Subject: | Bug #17563 Updated: PHP has encountered an Access Violation at 77FCB2A7 | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-9825@lists.php.net to get a copy of this message | ||
ID: 17563
Updated by: mfischer@php.net
Reported By: stanley@in2nett.com
-Status: Duplicate
+Status: Feedback
Bug Type: Unknown/Other Function
Operating System: WIN2K
PHP Version: 4.2.1
New Comment:
That's a start (and probably not a duplicte). But we need more
information. What vrsion of MSSQL ? And type was this field of ? Can
you reproduce this by creating a second field exactly as the first
which crashes, which crashes too ? Please be as detailed as possible
about the database setup and the field in general (so someone with the
appropriate environment can rebuild this scenery), thx.
Previous Comments:
------------------------------------------------------------------------
[2002-06-08 04:54:26] stanley@in2nett.com
GUYS!!!!!! Found it, as I said, there is one field have error, I remove
that field and add another field that is exactly the same datatype and
everything and the problem solved.
Try it out.
------------------------------------------------------------------------
[2002-06-08 04:46:44] stanley@in2nett.com
Ok, I found this error more specifically.
This error is actually from one of my database field, is "smallmoney"
allow null. but I have no idea why it have this error, because there
are exactly same datatype in the same table. I'll try to test more and
see.
------------------------------------------------------------------------
[2002-06-02 08:15:05] mfischer@php.net
Duplicate
------------------------------------------------------------------------
[2002-06-02 04:52:20] stanley@in2nett.com
I'm using MSSQL
when I use the SQL statement as "SELECT * FROM xxxxxxxxxxxx"
I will recieve that error, badly, but if I replace the * with whatever
field I need, I can avoid this error.
(notice my table has over 25 fields, small table seems working fine)
Not suppose to be like that, but well, I just found this way
works.......
Stan.
------------------------------------------------------------------------
[2002-06-02 04:14:51] stanley@in2nett.com
I'm using MSSQL
when I use the SQL statement as "SELECT * FROM xxxxxxxxxxxx"
I will recieve that error, badly, but if I replace the * with whatever
field I need, I can avoid this error.
Not suppose to be like that, but well, I just found this way
works.......
Stan.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=17563&edit=1