Sql Server Back-end with Access or Asp.net Front-end
-
I have data in a Sql Server DB. I want to put a basic front-end on this. The front-end would include a form for adding and updating records and having some reports generated from it also. Would Asp.net or Access be the best and quickest to develop front-end in this scenario?
-
I have data in a Sql Server DB. I want to put a basic front-end on this. The front-end would include a form for adding and updating records and having some reports generated from it also. Would Asp.net or Access be the best and quickest to develop front-end in this scenario?
That would depend entirely on your current skill set or ability to learn new stuff. Personally, I would use C# winforms or WPF for the presentation layer as the fact you are considering Access as a front end rules out ASP.net as that would imply an on-line solution. I wouldn't touch Access for the GUI with a very long barge pole.
-
I have data in a Sql Server DB. I want to put a basic front-end on this. The front-end would include a form for adding and updating records and having some reports generated from it also. Would Asp.net or Access be the best and quickest to develop front-end in this scenario?
How many people will use the front-end, and are they located in the same office? Will all your users be working on computers within a single LAN, or are they working from locations that are geographically distributed? How much control do you have over your users' deployment environment? A Microsoft Access front-end is almost certain to be the simplest and fastest solution to implement, but it comes with some limitations that are important to consider. I generally prefer ASP.NET because then the UI is accessible to anyone with a web browser. This makes the application easier to distribute and update - but it is likely to be more difficult and more time-consuming to implement.