Could you send a small (like one or two records) .dbf file
that exhibits that behaviour? I didn't see anything that
could cause that by just glancing at the code. 

I won't have time to look at it for a couple of days and I
am not a dbase expert though, so I do not assign this one to
myself, but I'll look at it.

Vlad

Well, that particular file in his database causes php to
return errorneous result (it adds a bunch of spaces in front
of the date, and messes up a couple of fields after that,
just appending them to the date field instead of placing in
the array as individual fields :( ).

I have a suspicion that the length of that particular date
field is not recognized properly, but the code is kinda
cryptic, so it'll take me a little while to figure that out,
if I can do that at all.

This was a malformed dbf file. It had a date field length
set to 0x08 0x02 instead of 0x08 0x00, which effectively
made this field seem to be 520 characters long instead of 8.

Some tools are smart enough to recognize that (Norton DBview
is one of them), but not php (or excel and some others for
that matter).

I'll see if I can make it more friendly so it recognizes
malformed files, but for now the bug is closed.

vlad@etl.ru, if you want to see a 'fixed' version of your
file, email me and I'll send you a copy with that 1 byte fixed.

Vlad