Should I Convert To Access 365??

[IC Clearly]

I have a legacy program that runs now on Access 2000 and 2003. I recently discovered that I can run that .mdb program under Access 365. In minimal testing it seems to run great. Is there any reason I should convert the 2000 DB (.mdb) to 365 (.accdb)?

Thanks.

[essaytee]

I am in a similar position where an app I developed many years ago, in the 90's, all the data files are still in .mdb format. The front-end on the other hand has been updated over the years, currently the deployment version is Acess 2010. For various table updates required over the years, the various front-end versions handled those with no problems whatsoever. I currently develop on Acess 2016 but when it comes to deployment, I open the development version in Access 2010, create the .accde file, test, and deploy.

I suppose you could defer to the old adage, "if it ain't broke, don't fix it".