使用SQL Server与Access窗体或ASP.NET [英] Using SQL Server with Access Forms or ASP.NET

问题描述

什么是采取一个大的（16000 LOC）现有的Access 2007 /表单应用程序并将其移植到SQL Server 2005，同时保持在前端的接入形式，与移植前端方式的利弊。 NET技术，说ASP.NET 4.0或MVC3？后端肯定是越来越移植到SQL Server，与大型架构修改，所以这个问题是关于是否使用现有的Access窗体前端与否。我不把扔掉现有的工作code掉以轻心！另一方面，模式将被改变很多。

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.

如果你有很多与ASP.NET/Oracle经验，但不能与Access或SQL Server，会如何改变这个答案？

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

推荐答案

有什么错Access作为前端的RDBMS是否SQL Server或其它

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

移植前结束，但留下一个Access后端似乎有点不可思议：何必呢？访问是一个很好的presentation工具，但平庸的DBMS。为什么要保持平庸？

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

这篇关于使用SQL Server与Access窗体或ASP.NET的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！