Hi Folks,
Just wondering what are the major differences between creating a front-end in access compared to a front-end with Visual Basic, .NET, and ASP on the web. It seems to me that many folks are fixated on .NET and ASP and don't realize that MS Access is very powerful and is capable of doing almost anything a .NET application can do. So I am a bit confused and wondering what are the real and true advantages/comparisons in using VB, .NET, or ASP over access for a front end when creating a moderate complexity database application/data-entry app that perhaps links several SQL Server tables together in SQL on the back-end. To me, access is much easier to grasp than the other possible mediums/solutions, maybe I am partial to it because it is cheap and fast/easy ... am I wrong? Also, with creating an app in VB or .NET it seems that the app would have to be tested on different OSs and systems and it can be very difficult to get all that to work together whereas in Access most of the times those issues do not exist. Also, is there any way anyone knows of, and I haven't found one yet, in which you can take access front-end and convert it to say .NET?
Thanks,
Joe
Just wondering what are the major differences between creating a front-end in access compared to a front-end with Visual Basic, .NET, and ASP on the web. It seems to me that many folks are fixated on .NET and ASP and don't realize that MS Access is very powerful and is capable of doing almost anything a .NET application can do. So I am a bit confused and wondering what are the real and true advantages/comparisons in using VB, .NET, or ASP over access for a front end when creating a moderate complexity database application/data-entry app that perhaps links several SQL Server tables together in SQL on the back-end. To me, access is much easier to grasp than the other possible mediums/solutions, maybe I am partial to it because it is cheap and fast/easy ... am I wrong? Also, with creating an app in VB or .NET it seems that the app would have to be tested on different OSs and systems and it can be very difficult to get all that to work together whereas in Access most of the times those issues do not exist. Also, is there any way anyone knows of, and I haven't found one yet, in which you can take access front-end and convert it to say .NET?
Thanks,
Joe
