Christopher Jolly

Actually, might have the same problem on ef6. It is experimental right now. Also perhaps should have a separate issue for ef6 experimental stuff

@bairog If the provider you have installed is x86 you have to target your project for x86. Similar for x64. It's just one of those things with using the access...

I think there have been some fixes in the 3.1 branch since this was merged to the main branch. Just to confirm those have been ported to the .Net5 main...

Can we close this topic? .Net 5 is already out of support so no use continuing on with this. Better to work on .Net 6/EF Core 6 and EF Core...

Also, being the identity column, it will affect any foreign key relationships as well. You may have to drop any relationships first, do the change, the recreate the relationships. That...

Oddly enough I ended up with this scenario against a SQL Azure database this week and got exactly the same error. So even the normal sql server migrations behaves like...

@dmitrybv Any success with using the 3.1-preview branch on net5.0? I did give it a go this weekend and while the main project that was using it compiled I did...

Can I ask what bitness you are compiling your program for? Any CPU,x86 or x64? It's just that `Microsoft.Jet.OLEDB.4.0` is somewhat legacy and only comes in an x86 version. If...

Thanks @bubibubi for that info. Also @xoniuqe just to confirm, if you already have a mdb file, you are able to connect to it using OLEDB? If not, go to...

@lauxjpn do you have the permissions to do the transfer? Also, recommend changing the default merge behaviour to squash and merge