What's strange about MS jet?

Kanas.net 1.3 is under intense testing. To ensure database support neutrality, adopt SQL standard to implement the worst MS Jet (MS Access 2000 format carrier, use ADO. Net oledb engine ). In the past, this type of database configuration was used less often, and its specific knowledge was not enough, resulting in inefficient troubleshooting.
One of the bugs in testcase went viral for an hour before they were found.

Let's take a look at the following two SQL statements with the same commands and different results:
Command text: Update debtors set debit = @ P3, searches = @ P4 where id = @ p2
Parameter table:
@ P2 = 16
@ P3 = 3650
@ P4 = 520
(The number of affected rows is 0)
Command text: Update debtors set debit = @ P1, searches = @ P2 where id = 16
Parameter table:
@ P1 = 3650
@ P2 = 520
(The number of affected rows is 1)
In SQL Server, such problems do not occur.