System.Data.OleDb.OleDbException (0x80040E10): No value given for one or more required parameters - (ADB repository using WIP release with EF Core 3.1.3)

@lauxjpn : I have tried with EF Core 3.1.3 and faced error: “System.Data.OleDb.OleDbException (0x80040E10): No value given for one or more required parameters.” Could you give me some advice? Note: I used your provider with ASPNET BoilerPlate fw.

_Originally posted by @ASCSolution in https://github.com/bubibubi/EntityFrameworkCore.Jet/issues/34#issuecomment-665571822_

---

@ASCSolution How does your .UseJet() call (and surrounding code) look like? Also, please post the full stack trace of the exception, the Linq query that fails and the SQL that is being generated an logged by EF Core.

(You might want to create a new issue for this.)

_Originally posted by @lauxjpn in https://github.com/bubibubi/EntityFrameworkCore.Jet/issues/34#issuecomment-665580535_

[lauxjpn]

@ASCSolution The configuration looks good as far as I can see. Please still add the Linq query and the generated SQL query (logged by EF Core).

In this case, please post both, the SQL query generated by the ABP repository and the SQL query generated directly by the context. Because it is unclear at the moment, whether the error comes from a wrongly supplied parameter or from a wrongly formatted query, it is important that you post the queries that are being logged by EF Core, not using the ToSql() method. (The ToSql() queries are parameterless and might therefore not be the exact queries that EF Core executes.) If you want, you can post both (so 4 SQL queries in total), but the SQL queries logged by EF Core are our primary focus at the moment.

You might want to add .EnableSensitiveDataLogging() and .EnableDetailedErrors() to your EF Core options builder for better logging output.

_Originally posted by @lauxjpn in https://github.com/bubibubi/EntityFrameworkCore.Jet/issues/34#issuecomment-666184307_

[horseyhorsey]

I found an unmapped property on the table. After adding entity.Ignore(x => x.MyUnmappedProp); in the builder it’s fine.