C # is a common development environment designed to create all the applications that can be understood.
Access is a development tool specifically designed for one purpose, i.e. creating front ends of databases.
All components inside Access are pre-created to simplify the interaction with data.
While, of course, there are libraries and controls available for C # that are designed to interact with databases, the less integration of the common development environment for the specific purpose of creating database applications.
Access to database related components is also more mature than anything that could be developed for C #, since Access was about twice as long. This also has its drawbacks, as some of the assumptions about how everything should work in Access also do not work in a modern environment (access was created before the network existed somewhere outside of academia).
I think it’s probably OK to select C # as the development platform for the database application if:
accessible developers are already familiar with C # database strings, and
you need to distribute your application to a very large number of users.
Access is quite difficult to deploy, and in large organizations, when you amortize the savings in RAD on a large number of desktops, it quickly overshadows the costs associated with Access deployment problems compared to a standalone executable without dependency execution time.
But we are talking about somewhere far above 100 desktop computers where the line crosses (and maybe closer to 500 or 1000), in my opinion.
source share