This is expected behavior; according to the manual[1]

| The number of items must be equal to the number of fields in the
| database, otherwise dbase_replace_record() will fail.

However, you're unsetting the 'deleted' field.

[1] <http://php.net/manual/en/function.dbase-replace-record.php>

According to the docs unsetting the 'deleted' fields is correct,
so I'm reopening.

The supplied test script can't work, because
dbase_replace_record() expects an *indexed* array, but $row has
been retrieved via dbase_get_record_with_names() what yields an
*associative* array. However, this should result in a "unexpected
error".

Anyhow, to analyze the issue further, we'd need a copy of a *.dbf
that causes this behavior. Please provide one for download.

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Re-Opened". Thank you.

I also get this error always. For my understanding, this simple code should work without problems:

$db = dbase_open('TEST.DBF', 2);
$data = dbase_get_record_with_names($db, 1);
dbase_replace_record($db, $data, 1);

But it will not work. All other dbase functions works fine.

Test file: https://www.dropbox.com/s/45d6u0k08pugm87/TEST.DBF?dl=0 (file type Fox Pro 2.x standard)

Tested with PHP 7.1.7 and 5.6.31

> For my understanding, this simple code should work without
> problems:

No, see the first example regarding dbase_get_record_with_names(),
<http://php.net/manual/en/function.dbase-replace-record.php#refsect1-function.dbase-replace-record-examples>

You are absolutely right! array_values was missing. Thanks.

Testing again with bigger dbf file today. Code:

$db = dbase_open('../ARTIKEL.DBF', 2); // 2 = lese und schreibmodus
$count = dbase_numrecords($db);

if($db){
	for($i = 1; $i <= $count; $i++){
		$row = dbase_get_record_with_names($db, $i);
		$row['L_MATCH'] = str_replace(" ", "", $row['L_MATCH']);

		if($row['L_MATCH'] == '33254'){
			echo '<pre>';
			print_r($row);
			echo '</pre>';

			#unset($row['deleted']); //doesn't work with or without
			$row['L_VERFUEG'] = 'TEST';

			$row = array_values($row);

			if(dbase_replace_record($db, $row, $i)){echo 'true';}else{echo 'false';}

			echo '<pre>';
			print_r($row);
			echo '</pre>';
		}
	}
	dbase_close($db);
}

I have exactly 150 values before and after using array_values but this error is coming again. So the problem must be something in the loop, isn't it? Topic opener had also a loop...

I found the problem.

Some dbf files have field types called "Memo". I have two of them in my "big" dbf file. The Memo fields are not loaded to the "row" array with dbase_get_record_with_names, dbase_get_record should be the same. So I have in total two rows less than required, that causes the error. So this causes a bug in some cases.

Solution is for me atm, to add the missed fields to the array AND assort it new or data will be wrong in the dbf file.

Screenshot with DBF Manager: https://www.dropbox.com/s/36quhybovgud3cz/jkghjfg.png?dl=0

> Some dbf files have field types called "Memo".

Ah, of course! Indeed memo fields are not really supported[1].
While they are recognized, they are never read. Quite a while ago
I tried to add support for memo fields, but that was a bottomless
pit – there are simply to many partly subtle differences across
different versions of DBase, FoxPro, etc.

Anyhow, since this is not a bug but rather a documented
limitation, I'm closing this ticket.

[1] <http://php.net/manual/en/intro.dbase.php>