I am currently playing around with this provider and recently updgraded from the 2.2.X release to the recently merged 3.1.
Until the merge I could use "MyContext.Database.GetAppliedMigrations()" successfully. Now the call raises :
System.Data.OleDb.OleDbException: 'Invalid SQL statement; expected 'DELETE', 'INSERT', 'PROCEDURE', 'SELECT', or 'UPDATE'.
I am using the following configuration for my context:
JetConfiguration.ShowSqlStatements = true;
JetConfiguration.DUAL = JetConfiguration.DUALForMdb;
JetConfiguration.UseConnectionPooling = false;
JetConfiguration.DefaultDataAccessProviderType = DataAccessProviderType.OleDb;
var lconnectionString ="Provider=Microsoft.Jet.OLEDB.4.0;Jet OLEDB:Engine Type=5;User ID=Admin; Data Source=\"<somevalidpath>\";Mode=Share Deny None;Jet OLEDB:Database Password=\"<somevalidpassword>\";";
optionsBuilder.UseJet(lconnectionString, OleDBFactory.Instance);
I tried some variations of this configuration:
- With and without
OleDBFactory.Instance
- With and without
JetConfiguration.DefaultDataAccessProviderType = DataAccessProviderType.OleDb;
Have I missed some obvious change in the framework or is this an bug?
UPDATE: I forgot to mention that I am using MDB files.
I am currently playing around with this provider and recently updgraded from the 2.2.X release to the recently merged 3.1.
Until the merge I could use "MyContext.Database.GetAppliedMigrations()" successfully. Now the call raises :
I am using the following configuration for my context:
I tried some variations of this configuration:
OleDBFactory.InstanceJetConfiguration.DefaultDataAccessProviderType = DataAccessProviderType.OleDb;Have I missed some obvious change in the framework or is this an bug?
UPDATE: I forgot to mention that I am using MDB files.