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. Sql-server-2008 programming tools development #Universal database front ends softwareĪny 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, 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. 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. #Universal database front ends software.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |