Converting an MS Access application to Visual Basic or C#

I have an invoicing application written in MS Access which needs to be converted to either a Visual Basic application or a C# application, I'm ok with both solutions. The application consists of the following: - 12 database tables - 2 queries (I did not preferer the query object, I preferred to use VB code to run my queries) - 19 forms, most of them with VB code behind - 12 reports (not all of them will be needed) - 4 modules All together there are around 3.300 lines of code behind the forms, reports and modules. The quality of the code I would say it is pretty good, well formatted, organized in a logical way, easy to read. There's no specification or documentation available for the software. So I can say that whatever functionality is available in the application, needs to be converted to the new one. Of course, I can make a short (but not detailed description) of what the software is capable of. But the scope of the project will not be defined by this description. The scope of the project is to convert each and every piece of code of the current application. The database tables should be kept in an MS Access database, just like now (now the db tables are organized in a separate database file, so the code and the db are separated) - so the database part does not need to be touched. The forms of the application are in Hungarian (and some of the variables also have a Hungarian name), but I can give you a simple translation of the forms, so you will understand the meaning of each field. The big question of this project: if possible, I would prefer (if possible) a solution which can be run as a standalone, executable application and as a web application at the same time. So in this ideal scenario there would be one single project from which I can easily build both an executable solution (basically an exe file) or a web application. The reason is that some of my customers need the solution as an executable file, other would like to use it as a web solution, deployed on my server. If this is too tricky or too costly, than the second best option is to have it as a web application, which can be either given to my customer and they will run it in a browser or I can deploy it on my web server. The least preferred option is to convert it to an executable application. So when you quote, please also provide: -which solution do you suggest and which solution your quote refers to -please, also let me know in a few sentences what would be the software architecture at the end I you'll do this development, what technology, what programming language are you going to use If you have any tools to convert the code to VB or C#, than probably 90% of the code can be converted automatically. Apart from this invoicing application I have a set of other, more complex applications written in MS Access. If this project is successfully done, probably I will request for a conversion of my other applications, too. So this project can be taken as a Proof of Concept.