ID: 39170 User updated by: cory dot nemelka at nemelkaitgroup dot com Reported By: cory dot nemelka at nemelkaitgroup dot com Status: Bogus Bug Type: dBase related Operating System: RHEL 3.0 PHP Version: 5.1.6 New Comment:
The smallest production file I have is 17MB (the file shown in hex). I can post a link if you'd like to look at it. If not, I'll figure it out sometime in the future and post the answer. It's clearly a byte-ordering problem. Since the files can't be opened by Msoft's products, I suspect that it is something local to our environment. Either way, PHP no longer reads *our* .dbf files. Previous Comments: ------------------------------------------------------------------------ [2006-10-17 09:08:58] [EMAIL PROTECTED] The file is currupted, even dbview is unable to open it. ------------------------------------------------------------------------ [2006-10-17 04:48:07] cory dot nemelka at nemelkaitgroup dot com previous version that could read these files was PHP v5.0.4, not v5.0.3. ------------------------------------------------------------------------ [2006-10-17 04:15:12] cory dot nemelka at nemelkaitgroup dot com Also, to clarify, the dbase_open function works fine with non-Visual Foxpro .dbf files. If you'd like, I'll dig into this further by downloading the C code for the dbase functions. lmk, --cnemelka ------------------------------------------------------------------------ [2006-10-17 04:11:29] cory dot nemelka at nemelkaitgroup dot com You can download a small .dbf file at the following url that should not open: http://tinyurl.com/yce3bn NOTE: The .dbf files that won't open will also not open in Excel or Access (they should). However, PHP v5.0.3? was able to open these files ok. ------------------------------------------------------------------------ [2006-10-17 04:08:54] cory dot nemelka at nemelkaitgroup dot com <?php $dbh=dbase_open("o1.dbf", 0); $ci = dbase_get_header_info($dbh); print_r($ci); ?> ------------------------------------------------------------------------ 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 http://bugs.php.net/39170 -- Edit this bug report at http://bugs.php.net/?id=39170&edit=1
