Actually, it seems to return only up to 254 fields, which is a bug on its own. I believe, there was a limit of 255 fields for dbase4 format. I do not believe this is the case with dbase5. 

This patch broke it: http://cvs.php.net/diff.php/php4/ext/dbase/dbf_head.c?login=2&r1=1.9&r2=1.10&ty=u

The simpliest way to fix that would be just to increase the constant from 254 to 1024. The better way would be figure out what the author of the patch meant by 'padded field headers'.

I'll look into that.


shoe@expressivetek.com, do you use dbase5? or something else?

Setting to 'Open' to prevent automatic closing due the no-feedback..

Vlad, what is the status on this?

didn't have time to look at PHP bugs for a while...

The status:
- No soul seems to know what 'padded field headers' 
- The only case when I can imagine it breaking is in dbase5 with [255...1024] fields (shoe@expressivetek.com did not prove or disprove that)
- I do not want to remove that padding algorythm, because obviously it worked for somebody.

The easy solution would be to just bump up the maximum number of fields. Memory consumption is not *that* much larger, it won't break anything, and, since dbase is dead, I am sure no-one will implement a version that has more than 1024 fields :)

I will do that once a check out a fresh tree. I'll close the bug when I do that.

I just bumped the number of fields to 1024 instead of 254 (which really should've been 255 in the first place). That *should* be the easy fix.

I see some indication (like here: http://www.dts.nl/support/helpdesk/bde/025/B22220007.htm) that dBase5 (at least for Windows) allows for 1024 fields. Finding real specs for dBase turns out to be pretty hard.

If that doesn't fix your problem, tell me what database you are actually using and re-open the bug.