Ralf Schmidt is totally right that using .NET can be very powerful and looking at the workflow as the OP posted in another thread here: Help with Run time error 91 it could be the way to go, since a selection is made with the tool which loads a form with a list of selected features allowing the user to select one of them and then it does something in Access.
BUT... I totally agree with James Crandall if you can change the workflow and move the data into a File Geodatabase a wealth of capabilities will be enabled.
A slide I like to include in my presentations on Python in the ArcGIS Platform is the one below:
... and yes, I truly believe that when you are not using Python you are probably doing thing the "hard way".
True that using .NET allows you to enhance the UI/UX of the workflow, but do you really want to introduce the additional complexity into your project.
To give you some pointers (based on a possible Python implementation):
BUT to show a list of features found in a form you will probably have to use something like TKinter.
The advance of Python is that you could make code that works for ArcMap and for ArcGIS Pro. You will not be able to do that with .NET, since ArcMap is based on ArcObjects and ArcObjects no longer exists in Pro.