Front End Dev

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQLServerCentral.com » Anything that is NOT about SQL! » Front End Dev

34 posts, Page 1 of 4

1 2 3 4 »»»

Front End Dev

Rate Topic

Display Mode

Topic Options

Author

Message

allen davidson

Posted Thursday, February 10, 2011 3:01 AM

Old Hand

Group: General Forum Members
Last Login: Sunday, March 17, 2013 7:53 AM
Points: 382, Visits: 784

HI all,

I'm very happy in my SQL world with all the tools MS give me.

Just sometimes somebody wants a small DB app developing, usually asap, usually for just a few people, usually fairly simple (a dozen 'screens' or so). In the past I have always defaulted to using Access - because its easy. But having a proper web app development environment would seem to make sense and overcome some of the limitations of Access. I played with VB .Net 2.0 a few years back but didn't stick at it long enough to get productive.

So the question is; what would you recommend?

Cheers
Allen

Post #1061787

er.alok

Posted Thursday, February 10, 2011 3:17 AM

Forum Newbie

Group: General Forum Members
Last Login: Friday, January 18, 2013 3:47 AM
Points: 2, Visits: 95

Hey Allen,

It is always advisable to go with Sql Server, even for a small database also.
Access is strictly not advisable if the data is confidential you want to store because sql injection is possible in access.

Post #1061802

daniverz

Posted Thursday, February 10, 2011 3:30 AM

Forum Newbie

Group: General Forum Members
Last Login: Thursday, March 28, 2013 9:08 AM
Points: 4, Visits: 28

Hi,

I've been there. Believe me: SQL. For any size of application. It really pays off in Web environment as well as in local Windows applications. Throw in SQL Express and shazam.

The real difference is the database programmability, that you don't find in Access. Procedures, Functions, Triggers and so... real development accelerators :)

DV

Post #1061809

allen davidson

Posted Thursday, February 10, 2011 3:36 AM

Old Hand

Group: General Forum Members
Last Login: Sunday, March 17, 2013 7:53 AM
Points: 382, Visits: 784

Thanks - I was probably not very clear, I just use Access if I need a front end. The back end is always SQL. A lot of my DBs are Data Warehouse type setups where they do not have a traditional front end (data is loaded and processed batch using SSIS & SSRS).

Just sometimes I get asked for a desktop type app, something to keep track of widgets for the companies widget department, they want simple data entry screens and selection screens (and screens with grids).

Cheers
Allen

Post #1061812

daniverz

Posted Thursday, February 10, 2011 3:45 AM

Forum Newbie

Group: General Forum Members
Last Login: Thursday, March 28, 2013 9:08 AM
Points: 4, Visits: 28

Oh...

In this case Access is for sure an alternative. I use the SQL Server Reporting Services to create readonly interfaces (grids) from data. When a more elaborated interface is needed, a very simple path is a Visual Studio ASP.NET MVC project. With very few code you can produce very nice database interfaces.

DV

Post #1061817

SQLSmasher

Posted Thursday, February 10, 2011 3:54 AM

SSC Veteran

Group: General Forum Members
Last Login: Tuesday, April 26, 2011 8:38 AM
Points: 215, Visits: 104

Thsts all depend on new application requirement. If you feel client you can keep client happy with using SQL Server Reporting Services front end that is wonderfull and will avoid all hassle of coding new application.

But like few year back i have to create web application front end using ASP.NET for our lcient, because they are expecting parameter behaviour which is not possible using SSRS.

Post #1061825

Brandie Tarvin

Posted Thursday, February 10, 2011 11:59 AM

SSCertifiable

Group: General Forum Members
Last Login: 2 days ago @ 12:35 PM
Points: 6,650, Visits: 5,666

Access, as a front end, has always caused problems as a straight .mdb linked database. At least, it has for me. The connection is always slow (not SQL Server's fault) and security is iffy at best. You can't kick people out of Access if the database gets corrupted and, if you're using group security, it can be difficult at times to tell who is really in the Access database.

Also, the people in Access can do all sorts of funky things like try to Repair and Compact the database while others are in it...

Using an Access .adp for the front end is better, but not entirely optimal. I don't know if it's just our version that we're about to lose support for, or what, but I do know that when we upgraded SQL Server and the Office tools didn't keep pace, it made the interface cranky.

So, whatever you decide, make sure you test it thoroughly and account for future software changes when you make that choice. Because you'll be stuck with your decision for quite a while, unless you have unlimited technology budget funds.

Brandie Tarvin, MCITP Database Administrator, MCDBA, MCSA

Webpage: http://www.BrandieTarvin.net
LiveJournal Blog: http://brandietarvin.livejournal.com/
On LinkedIn!, Google+, and Twitter.

Freelance Writer: Shadowrun
Latchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

Post #1062230

GSquared

Posted Thursday, February 10, 2011 12:09 PM

SSCoach

Group: General Forum Members
Last Login: Monday, May 06, 2013 1:09 PM
Points: 15,439, Visits: 9,569

If you want to stick with something similar enough to Access to be easy to learn, but more robust, secure, et al, go with VB.NET. That'll give you good client-server apps.

If you want to move into web pages for the interface, go with C#.

Those aren't hard-fast-rules, those are my opinions.

- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread

"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

Post #1062238

Brandie Tarvin

Posted Friday, February 11, 2011 4:16 AM

SSCertifiable

Group: General Forum Members
Last Login: 2 days ago @ 12:35 PM
Points: 6,650, Visits: 5,666

I almost forgot to add my favorite Access activity. Creating new tables in Access that aren't in SQL Server (without telling anyone), than getting upset when another user deletes that table and expecting the DBAs to have a backup from SQL.

Brandie Tarvin, MCITP Database Administrator, MCDBA, MCSA

Webpage: http://www.BrandieTarvin.net
LiveJournal Blog: http://brandietarvin.livejournal.com/
On LinkedIn!, Google+, and Twitter.

Freelance Writer: Shadowrun
Latchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

Post #1062460

pvanitallie

Posted Thursday, September 20, 2012 3:09 PM

Forum Newbie

Group: General Forum Members
Last Login: Monday, October 29, 2012 8:16 AM
Points: 8, Visits: 28

I have been looking for something in a Visual Studio-type product as a way to convert an existing MS Access Front End to a SQL Server back end with nearly 100 users on multiple sites.

I like the rapid application development tools that Access provides and can still be used by people who are using Office 2003. But the world is changing. A Web front end is going to provide a more uniform response time and no need to update the front end at each work site. I expect to use SharePoint to do the authentication that is provided by Active Directory (so that the application does not have to authenticate users).

I have not been able to find a set of tools that will let me have the forms with drop down boxes, command buttons, text displays and waterfall displays that are easily added and customized for Access. But I have not found anything suitable in my search so far; I have experience using Visual Studio. I've tried several ASP.NET tutorials and usually can make them function but cannot find a way to mimic the simple functionality of MS Access to display, update and add to the data in a SQL Server database.

What do you recommend?

Post #1362340

« Prev Topic | Next Topic »

34 posts, Page 1 of 4

1 2 3 4 »»»

Permissions