Is there a front end application development tool for sql server 2008 R2?
Hello all, I need to know if there is an application in which I could develop a front end to SQL Server 2008 R2? I will try to clarify what I am needing (I am only needing to develop an application for practicing purposes, not for a production environment right now). For instance, I have created a table in SQL Server 2008. I need a front end application that will let me add a person, delete a person, total expenses total expenses for a particular person(such as travel expenses, hotel expenses, etc.), search for a particular person by name or id. I know how to write SQL code to do all of this on the backend, but I am just needing an application in which I can develop a front end to do all of thiswith the use of buttons, search boxes, etc. I do not know if I can develop something like this using SSRS. I do not want to use FileMaker because I have had pretty bad experiences with FileMaker. Any suggestions on the type of software that I could use to develop something would be greatly appreciated.
It sounds like you need a custom written application. I'm not an application developer, but I'm sure that you can do this in just about any language (ASP .Net, VB .Net,C#, ADO .net, etc) that has the ability to call either stored procedures or hit the objects (tables/views/etc) via tools like Entity Framework. I'm not aware of any type of application that would allow you to build this out in the manner in which I think you are asking. Other on here might though. You also might be able to search around on the Interwebs and see if someone has already built a product that would suit your needs at a price. Why reinvent the wheel if you don't have to? I don't believe that you can do this in SSRS, but I also don't claim to be an expert in it. While I don't like it, you can use MS Access as a front end to SQL Server. It is a viable solution depending on your requirements. I would strongly evaluate it first before going down that road, but as I mentioned, it is a viable option. Not sure if this helps or not, but just some things to think about.
I know I'm somewhat echoing Ken and John here, but I think I can add something useful that doesn't go well in comments. The key is that you can write a front end of the type you are describing in just about any full programming language. With that in mind, the questions are twofold: Which languages do you know or are you prepared to learn for this? Of those, does one provide a clear advantage? Some good options include: **Access** If you are planning for this to run locally on the machines (not over the web) and it will be fairly simple, Access is probably a very good option. I would never use it for a major project, but it is extremely intuitive, has very good help files, synchs very easily with SQL Server (especially if you built the DB in Access and migrated, slightly harder but still not hard if you are attaching Access to a preexisting DB). You can very readily learn what you need while you are working on your project with little prior experience. It also tends to be very comfortable for many users and you can give your "power-users" the ability to look at the raw tables and write their own queries with absolute no additional work. The bad thing is that it is plainly unsuitable for large projects or for projects where perofrmance is a major issue, but I still use it occassionally for small one-off projects, especially if the target users are power-users that I know like to be able to glance at the base tables from time to time. If you have no programming experience outside of SQL itself, want to build this fast, think it qualifies as a small project, and don't mind running it locally (IE no web interface) then I strongly recommend Access. **Lightswitch** I have never used Lightswitch, so take this with a grain of salt. From what I have seen, Lightswitch is a fantastic product for a certain niche - Mostly PowerUsers that are not and do not want to be serious programmers, but want to be able to quickly and easily create a basic interface to a database and some reports. Unlike Access, you can also readily create something with a web interface. If you do not know how to program, don't want to learn to really program (or don't have the time right now), and need a web interface, LightSwitch sounds perfect. Otherwise I would look at other options. **C#** C# is a versatile, effecient language that integrates well with SQL Server by design. It can scale to handle projects of virtually any scope and can make local programs or web based interfaces. It generally comes with the excellent Visual Studio IDE which helps shield you from the need to memorize details of every command. Knowledge of C# will serve you very well outside of any one particular project The downside is that it has a steeper learning curve than most other options. It has a much steeper learning curve than Access, or Lightswitch (from what I hear). Its learning curve is also steeper than Python which I'll get to next. With that said, its not that hard to learn for someone that has a little bit of programming experience. **Python** [Python] is my personal go to language unless I have a good reason to use something else. It works well with SQL Server and is great for [data visualization], especially if that data needs some real processing before display. For a full programming language, it is extremely easy to learn, works well to replace shell scripting (I started using Python for that before PowerShell was released), and a knowledge of Python would likely serve you very well. With all that though, there are a couple of downsides. For one, its easy to learn compared to C# and most general purpose programming languages, but harder to learn than access. The other is that the performance is worse than C#. Also, all the other tools I mentioned are explicitly designed to work with SQL Server. Python works with it very well, but it was not a design goal. :
What I would add to the options mentions in other answers is that you should choose something that can be easily supported by you and your colleagues. Creating something that cannot be maintained or developed further in the future then there is limited worth in using that technology now. For me, Access will be the fastest way, using Linked Tables, followed by Visual Studio to develop an application of your choice in a language of your choice.
I'm surprised no-one has yet mentioned Notepad (or another text editor) as a development tool... You can use it to write vanilla ASP applications. I've done this too many times for it to be my first recommendation, but it has the benefits of being near-universal and cheap.
(I think the latter is the reason I was forced to use it for so long... bloody lawyers...)