选择 Web 应用程序框架来替换 VB6 和 Access 应用程序
我目前在一家大公司工作，该公司拥有相当多的 Access 数据库。他们已经安装了 SQL Server。现在我的任务是迁移数据库并最终迁移应用程序。它们全部都是用 Visual Basic 6 编写的。我和另外 2 个人一起工作，他们只知道 VB6 并且并不真正渴望学习其他任何东西。另一件需要记住的事情是，在这种情况下，快速开发比稳健性更重要。尤其是在报告功能方面。我在 Java/Spring/Hibernate 方面有很强的背景，但我真的不认为这是一个好的选择，因为 java 应用程序的开发时间通常比其他应用程序长，而且对于其他人来说，学习 VB6 有点困难。欢迎所有建议！
I am currently working at a large firm which has quite a lot of Access databases. They already have SQL Server in place. Now it's my task to migrate the databases and eventually the applications as well. All of them written in Visual Basic 6. I work with 2 other people who know only VB6 and are not really eager to learn anything else. Something else to keep in mind is that rapid development in this case is more important than robustness. Especially when it comes to reporting capabilities. I have a strong background in Java/Spring/Hibernate but I don't really think that's such a good choice, since development time in java apps is generally longer than other and it's kind of a stretch from VB6 for the others to learn. All suggestions are welcome!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我的情况几乎相同。我开始使用 5 个左右的“纯”访问应用程序，即前端是 access，后端是 JET。我所做的是使用两步过程。首先，我将数据迁移到 SQL Server，同时保持前端相同。
一旦我对此感到满意，我就开始一次将一个应用程序转换为 asp.net Web 应用程序或 vb.net 客户端应用程序，具体取决于最适合的应用程序。
对于报告，我使用了 SQL Server 2008R2 附带的优秀报告生成器 3.0。
从 VBA 到 vb.net 的跳跃仍然是一个变化，特别是如果您习惯使用 DAO/ADO 进行数据访问，因为 ADO.net 是一个完全不同的野兽，但一旦您明白了，事情就相当简单了，
这就是我的故事我在你的情况下经历过的事情，希望它有所帮助
编辑：这是我经历的一些选择过程。
这取决于谁将使用它以及所需的功能集。
我可以告诉你两个例子。
第一个是名为“Breach Light”的应用程序，它允许每个人（400 个用户）记录他们在过程中遇到的违规行为。它的 3 种简单的数据捕获形式很少被大量用户使用，因此它将成为一个 Web 应用程序，因此我获得了无需安装和轻松更新的好处，而缺点也并不那么重要。
第二个是一个由大约 20 个人使用的富客户端，它负责所有呼叫预测等工作。该客户端将是一个 vb.net 桌面应用程序，以提供更好的用户体验。
就像所有课程都需要马一样，当人们说“网络应用程序适合一切”或“我讨厌网络应用程序，胖客户端适合所有人！”时，我确实很恼火。使用正确的工具完成正确的任务
I’m in almost the same situation. I started out with 5 or so “pure” access applications i.e. the front end was access and the back end was JET. What I did was to use a 2 step process. First I migrated the data into a SQL server whilst keeping the front end the same.
Once I was happy with that I started converting one application at a time to either an asp.net web app or a vb.net client app depending on what was the best fit.
For the reporting I used the excellent report builder 3.0 that comes with SQL server 2008R2.
The jump from VBA to vb.net is still a change especially if you are used to using DAO/ADO for data access as ADO.net is quite a different beast but once you get your head round it things are quite simple
Well that’s my story of what I went through in your situation, hope it helps
EDIT: This is some of the selection process I go through.
It would depend on who is going to be using it and the feature set that is required.
There are two examples I can tell you about.
The first is an application called “Breach Light” it is used to allow everybody (400 users) to log breaches in process they come across. Its 3 simple data capture forms used infrequently by a large user base so it is going to be a web app so I get the benefits of no install and easy update and the downsides don’t matter so much.
The second on is a rich client used by 20 or so people that does all of the call forecasting etc. That one is going to be a vb.net desktop app to allow for a better user experience.
As with everything its horses for courses, it does annoy me when people say “web apps for everything” or “I hate web apps, thick clients for all!”. Use the correct tool for the correct task
对于任何想要在未来继续支持 VB6 代码的人，我强烈建议您查看 REAL Studio（以前称为 REALBasic） http://www.realsoftware.com/
这是一个非常优秀的软件包，与 VB6 非常兼容 - 特别是与 Windows 功能套件结合使用：http://www.arbpmembers.org/windows-functionity-suite
其他库添加了大量功能：http://www.monkeybreadsoftware.de/realbasic/plugins.shtml
这里列出了更多库和控件：http://www.rbgarage.arbpmembers.org/rbg/
此外，我相信它具有 COM 互操作性，因此您应该能够继续使用您购买的任何自定义 COM 控件。
最后，RB 现在可以部署到 Windows、Mac OS X、Linux，甚至可以作为独立的 Web 应用程序服务器。这是一个非常灵活的平台，VB6 程序员很容易转换到该平台，并且拥有相对较大的开发人员社区。
我用一个下午的时间将一个相对复杂的VB6应用程序（实际上是一个最初用VB3编写的文本冒险游戏引擎）移植到REALBasic上，遇到的麻烦很少。
For anyone in the situation of trying to continue supporting VB6 code into the future, I would strongly recommend looking at REAL Studio (formerly REALBasic) http://www.realsoftware.com/
It's a really excellent package that is very compatible with VB6 - especially in combination with the Windows Functionality Suite: http://www.arbpmembers.org/windows-functionality-suite
Other libraries add massive sets of capabilities: http://www.monkeybreadsoftware.de/realbasic/plugins.shtml
Many more libraries and controls are listed here: http://www.rbgarage.arbpmembers.org/rbg/
Additionally I believe it has COM interop so you should be able to keep using any custom COM controls you have purchased.
Finally, RB can now be deployed to Windows, Mac OS X, Linux, and even as a stand-alone web application server. It's a very flexible platform, would be easy for VB6 programmers to convert to, and has a relatively large community of developers.
I ported a relatively complex VB6 application (actually a text adventure game engine originally written in VB3) to REALBasic in an afternoon with minimal trouble.
我认为迁移到 VB.NET & 是最容易的。 ASP.NET/WEB FORMS，如果考虑到当前的VB6开发人员。
VB.NET 与 VB6 不完全一样，但比 java 更接近。
另外，asp.net web-forms 遵循 winforms 模型，因此会更容易。
但总体而言，他们将有一个掌握 .net 和 Web 开发的学习曲线。
如果他们使用 Access，是否也会使用 VBA？
或者雇用新的开发人员并使用您喜欢的东西:)
因为不渴望学习新事物的开发人员低估了自己。
I think it would be the easiest to migrate to VB.NET & ASP.NET/WEB FORMS, if you take into account the current VB6 developers.
VB.NET is not completly the same as VB6, but it's closer than java.
Also, asp.net web-forms follows the winforms model, so that would be easier to.
But they will have a learning curve grasping .net and webdevelopment in general.
If they use Access, would the also using VBA?
Or hire new developers and use what you are comfortable with :)
Because developers not eager to learn new things are selling themselves short.