moveTo($offset) gives the wrong row with some DBF files about php-xbase HOT 8 CLOSED

So, I have investigated this a bit further.
It would seem that DBF files have some "duplicate" rows that are invisible to LibreOffice if it reads it in DBF format. They do show up if you convert the DBF file to CSV before reading (I did this with a small python script, https://gist.github.com/bertspaan/8220892).

At this point I'm not sure if this is an issue with the way LibreOffice handles DBF files, or if it's something to do with xbase.

from php-xbase.

I think you should check opening the original DBF file directly with a DBF viewer, rather than LibreOffice to see if the duplicates where there in first instance

from php-xbase.

LibreOffice is a DBF viewer in that sense. When it's a DBF file I'm opening, the duplicate rows are not there. But that isn't the same as the xbase output, as the output does include the duplicates.

from php-xbase.

how do you use

moveTo($offset)

what value do you give to that function?? I want to use it but don't know which value to give it, so it can move to the row I want to

from php-xbase.

$offset is the row you want to move to. So, if you want to keep moving forward, you need to increase the $offset since the last time you used it.

from php-xbase.

but what determines the number of the row? for example, if I want to move to the record where id=1221. Does it uses a some sort of index? because DBFs do have index files that accompany them (INX files)

from php-xbase.

The number of the row is the row in the DBF file. So, if you're looking by ID, you need to first know where that ID is. Which probably means you need to go through the entire file first.

Best way to go about using these files is to import the entire thing into a database table, and then run any SELECT queries on the table itself.

from php-xbase.

I don't think it's still actual

from php-xbase.