Migrating an Access 2002 Application Front-end to Access 365 or SQL Server.

Jayeff Well we give a lot of material to discuss ....

Lets try to clear some...

At first what kind of errors you get ...some screenshots and some more info would be most helpful.

If you are migrating from Access 2002 to a 64bit version then you will encounter severe issues due to changes in the .dlls declaration and lack of many ActiveX controls.

Now as for the actual question ...why to migrate to a newer version..... the answer would be that you want to be on a newer version...while the only significant change at first glance is the Ribbon and some graphics effects...it seems that under the hood there are some small changes that allow for better functionality.

Last but not least....your mention about problems,corruption ...etc. means that you have issues...what/why it needs investigation...but i can tell you that for sure...just switching to SQL server for BE ...it isn't going to resolve problems...it would rather add some new interesting ones...SQL server is a total different story than Access...unless you treat/handle it the way is meant to be treated/handled it will far more issues...not to mention being slower in many cases ...BUT if you "switch" to SQL philosophy the performance would be stellar.

You mentioned about .mde....this is not "migration" ...you just using the old application via the newer Access...you must "migrate" everything to the newer format (.accdb/.accde)