Quote Originally Posted by kutlesh View Post
Yes I mixed two questions. Probably more appropriate is to upgrade old Access 2000 apps to the new Access 16.

EDIT:

Hmm, why I bother so much. Just upgrade the old apps in new Access.

I asked this question because a thought crossed my mind. If you have ton of VBA code in Access 2000, what would you do to rework it in other newer and more powerful technology... Access is not very attractive.
No new young programmers would like to work in Access VBA, sadly
There is a bit of nuance to this question you're asking. You can't think in terms of converting VBA to C#/VB.Net. You see, VBA is more than just a language. It's an entire environment designed to help automate tasks within the Office Suit of products like Word. VBA is used within Access and as far as I know, it has no bindings to .Net. In this case there is no need to translate anything.

However, Microsoft Office exports COM objects that allow you to control various thinks like Word documents and Excel spreadsheets from external applications. In this case, you question makes a lot more sense. You could write an application in C# that use these COM objects to interact with Office. You could have VB6 code that does the same thing that could be translated to VB.Net.

TLDR;

VBA is internal to Office and is based on COM. You can only use what Office allows you to use. If it doesn't allow you to use the .Net Framework or .Net Core then the question is moot. You stick with VBA.