使用Windows GUI寻找基于SQL的RDBMS [英] Looking for a SQL-based RDBMS with a Windows GUI

问题描述

我有一个20年前用MS-DOS 5.0的INFORMIX-SQL 2.10版开发的应用程序.我可以在Windows Vista下的Microsoft Virtual PC 2007中的MS-DOS 6.22上工作，但是我想使用基于WINDOWS的RDBMS重新编写此应用程序.

I have an application I developed 20 years ago with INFORMIX-SQL version 2.10 for MS-DOS 5.0. I have it working on MS-DOS 6.22, within Microsoft Virtual PC 2007, under Windows Vista, but I would like to re-write this application with a WINDOWS-based RDBMS.

我正在寻找功能与notifyix-sql类似但适用于Windows的产品

I'm looking for a product, similar in functionality to informix-sql, but for windows which:

1. 将生成不需要运行时的免版税(.exe)程序.
2. 快速创建屏幕，报告，存储过程(应用程序生成器)的原型.
3. 集成开发环境.
4. 丰富的功能.

我看过:

1. 四个Js
2. Visual FoxPro
3. 访问
4. Oracle

有什么建议吗?

推荐答案

访问符合此要求，但需要运行时.

Access fits this bill with the exception of needing a runtime.

我无法想象任何不需要某种类型的运行时的不错的RAD开发工具.我的意思是，即使回到FoxPro DOS时代，您仍然必须提供运行时，并且要开发从VB6到VB6的所有版本的VB，那么您必须确保并提供运行时(另一方面，它非常庞大).帮助Windows XP，Vista和Windows 7都附带了Visual Basic运行时.

I can’t imagine really much of any decent RAD development tool that does not require some type of runtime. I mean even going back to FoxPro DOS days, you still had to provide a runtime, and for development of all versions of VB all the way up to VB6, then you had to ensure and provide a runtime (on the other hand, it immensely helped that Windows XP, vista, and windows 7 all shipped with visual basic runtimes).

实际上，即使使用.net开发来生成可执行文件，也必须再次安装运行时系统.

In fact, even when you produce executables using the .net development, again you have to install a runtime system.

请记住，可执行运行时系统的一大优势是，一旦将运行时系统安装在目标计算机上，那么您的更新就只是x-copy开发范例.因此，这意味着对软件的每次更新都只是新程序的副本，而无需支持库.

Keep in mind that one great advantage of an executable runtime system , is once the runtime system is installed on the target machine, then your updates are simply a x-copy development paradigm. Thus means each update to your software is simply a copy of a new program without needing the support libaries.

例如，Access有一个了不起的而且非常丰富的报告系统.一旦安装了运行时.然后，您的软件的每次新更新都会导致最终应用程序大小的增加很小甚至很小.通常，部署该新应用程序的规模通常很小.重新部署和重新发布该应用程序环境所需的所有运行时位和片段是没有意义的.对于运行时系统，您只需执行一次即可.

For example Access has a terrific and very rich reporting system. Once the runtime is installed. Then each new update to your software will result in very small if any growth at all in the resulting application size. Deploying that new application will generally as a rule be very small in size. It does not make sense to redeploy and reissue all of the runtime bits and pieces that that application environment requires. With a runtime system you only do this ONCE.

因此，尽管需要运行时系统有一些缺点，但也有一些重大的缺点.当您为软件提供许多频繁的更新时，这些优势尤其明显.当然，一旦开发周期完成，并且软件的更新和新功能请求变得十分罕见，那么我肯定会承认拥有独立的可执行系统具有其优势.

So while there are some downsides of requiring a runtime system, there are also some significant upsides. Those advantages particularly show themselves when you’re offering many frequent updates to your software. Of course once the development cycle is complete, and updates and new feature request become quite rare for your software, then I would certainly concede that having a stand alone executable system has its advantages.

在大多数情况下，我们的整个软件行业的综合哲学和方法远远落后于独立可执行文件的概念.因此，当今几乎任何体面且高效的开发环境都将需要各种条件，例如与网络的连接，丰富的报表编写者等.

For the most part the combined philosophy and approach of our WHOLE software industry has much left behind the concept of a stand alone executable. So, Just about any decent and productive development environment today will require all kinds of things like connectivity to the web, rich report writers etc.

说句公道话，趋势是我们所谓的应用程序虚拟化应用程序或应用程序流传输，其中在具有多个依赖项的复杂应用程序中将其部署为单个.exe.但是，尽管将应用程序部署为单个.exe，但是用于创建该.exe的开发范例和工具仍然需要将该功能包含在功能丰富的运行时程序包中，该程序包仅对OS隐藏，并且此应用程序虚拟化概念确实可以确实很好地解决了.dll损坏和依赖性问题.

To be fair there is a trend towards what we call application virtualization application or app streaming in which in a complex application with many dependencies is deployed as a single .exe. However, despite deploying the application as a single .exe, the development paradigm and tools used to create that .exe still requires a Feature rich runtime package to be included with that .exe, it just hidden to the OS and this application virtualization concept does solve the .dll breakage and dependencies issue very well indeed.

所以Access提供了完全免费的发行版，但是您必须生成包含运行时的安装软件包.

So Access offers completely royalty free distribution, but you have to produce you install package that includes a runtime.

但是，我可以说这与我们多年来使用Visual Basic，旧的DOS FoxPro或现在的.net确实有很大的不同.公平的说，您需要一个运行时，并一直回到Foxpro或DBASE时代.

However I can say this is really much different than what we’ve had for many years with visual basic, the old DOS FoxPro, or now .net. It standard fair you need a runtime, and going all the way back to Foxpro or DBASE days that was also the case.

这篇关于使用Windows GUI寻找基于SQL的RDBMS的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！