February 10, 2010 at 10:07 am
Hello everyone,
I stumbled across this post from last year:
http://www.sqlservercentral.com/Forums/Topic657618-1292-1.aspx
My background is from IT and was given the task of learning\developing\maintaining a db for my department and importing data that was on an approach db.
I picked up a copy of MS Access and some books. I was instantly hooked. I enjoyed all aspects of working with an DBMS: Data Modeling, GUI design, etc...
At present, I want to build a new project in SQL Server 2008 Std. and I don't want to use MS Access as a client due to its security structure, Access 2003 anyway.
I'm aware some use PHP, .net (ASP, VB, C#) none of which I'm disciplined in. What else is available without a steep learning curve? Which one do you use and why?
One of the good things about Access is that it provides both the BE & FE.
Thanks in Advance for your help. 😀
-me2
p.s. Any new learning resources would be greatly appreciated.
February 10, 2010 at 10:12 am
What's your project? ASP.NET might be the easiest.
If it's just reporting, SSRS fits.
February 10, 2010 at 11:03 am
Hi Steve,
It's more than reporting I'm afraid.
I've used VBA in Access but I felt somewhat intimidated with asp.net after looking at some code.:unsure:
Primarily, the project is a Process Data & Documentation DB but not limited to it. It will eventually expand to encompass other aspects that at the moment are on paper.
I basically want to develop a web base app w/ SQL Server as the BE.
I would prefer to have a fancy/rich GUI look like something out of Access 2007 but without Access. 😉
-me2
February 10, 2010 at 12:08 pm
Not sure why you don't want to use Access as front-end when you keep saying you like it 🙂
If you are concerned about security you can always handle security at your back-end SQL Server database.
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.February 15, 2010 at 6:35 am
Hi PaulB,
Well.....I guess I'm partial to MS Access because that's where I learned the basics...:-)
but security is the main reason I'm looking at other solutions for the FE.
Besides that, I also wanted to pursue to develop a web UI for this project & I'm always willing to learn something new.
February 15, 2010 at 6:45 am
I agree with PaulB. Access does have it's limitations, but security shouldn't be one of them because you can delegate that to a different layer such as the db. I haven't used access in a while because I mostly do the plumbing now but from what I remember, there was no easier way to build a general purpose front-end. If your app is internal and you are running on ActiveDirectory security, then you can leave your access app completely insecure and still lock out the bad guys just by not giving them access to the back end DB though the DB's security layer.
Tim Januario
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply