Using SQL Server with Access Forms or ASP.NET

Question

What would be the pros and cons of taking a large (16000 LOC) existing Access 2007/Forms application and porting it to SQL Server 2005, while keeping the Access forms on the front end, versus porting the front end to a .NET technology, say ASP.NET 4.0 or MVC3? The backend is definitely getting ported to SQL Server, with large schema modifications, so this question is about whether to use the existing Access Forms front end or not. I don't take throwing away existing working code lightly! On the other hand, the schema will be changing a lot.

If you had a lot of experience with ASP.NET/Oracle but not with Access or SQL Server, how might this change your answer?

Thanks,
Mike

This statement may be a bit of a mis-direction: "I don't take throwing away existing working code lightly!" Most likely your "major schema overhaul" would force extensive changes to the existing Access front-end. So more accurately the choices you're considering are major revision to Access front-end vs. using Dot Net for the front-end. — HansUp
– HansUp, Commented Jul 14, 2011 at 14:05

gbn · Accepted Answer · 2011-07-13 21:16:39Z

3

There is nothing wrong with Access as a front-end to an RDBMS whether SQL Server or another

Porting the front-end but leaving an Access back-end would seem a bit weird: why bother? Access is a good presentation tool but mediocre DBMS. Why keep the mediocre?

Also, only change one component at once no matter what you do: data, then front end. Don't do a big bang approach and change the lot

edited Jul 13, 2011 at 21:16

answered Jul 13, 2011 at 21:02

gbn

434k84 gold badges602 silver badges690 bronze badges

Sign up to request clarification or add additional context in comments.

8 Comments

Mike Over a year ago

We would definitely use SQL Server as the back end no matter what, I edited the question to make that more clear. I am a C# guy, but I don't want to let that sway me from staying with a VB/Access/Forms solution if it makes the most sense.

gbn Over a year ago

@Mike: my answer still holds, I'll add more though

Mike Over a year ago

Please do if you could give some specifics that I could use as concrete justifications. :)

Mike Over a year ago

The schema is going to be revised dramatically, which would cause a lot of code changes anyway. At some point it must make sense to migrate away from Access. But I have no feel whatsoever for where that point lies. Basically I have no idea how friendly or how testable Access apps are.

gbn Over a year ago

Why not hide the schema changes behind views so Access sees the same?For writes, use INSTEAD OF triggers to capture them

|

Igor Turman · Accepted Answer · 2011-07-14 07:05:45Z

1

Actually, comparing going with web application (ASP.NET) and stand-alone (Access) is not truly "apples-to-apples" comparison. It highly depends on your requirements.

Sure, going with web application will require much more developer's efforts comparing to building forms/reports in Access. But, the pay-off will be felt in the mid to long term.

You should also consider scalability, deployment, and availability issues when deciding to go/stay with Access.

answered Jul 14, 2011 at 7:05

Igor Turman

2,2151 gold badge23 silver badges26 bronze badges

Collectives™ on Stack Overflow

Using SQL Server with Access Forms or ASP.NET

2 Answers 2

8 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

8 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related