IDS对单用户应用程序的过度杀死？ [英] IDS an over-kill for a single-user app?

问题描述

我有以下dilema：我的客户（妈妈流行当铺）一直在使用我的mgmt。系统，开发与ISQL，超过20年。在这二十年中，我已经为每个客户的愿望定制了应用程序，或者当法律/法规的变化需要它时。大多数客户端是单用户站点。一些有多个商店，但从来没有想要一个分布式数据库，不信任互联网或任何其他类型的网络的可靠性或安全性。所以，他们都使用标准引擎。我已经能够解决一些SE限制，并做了一些聪明的技巧与ISQL和SE，但迟早，新法律可能需要当铺客户，商品，电子传输等的图像，然后它的时间升级到IDS，在4GL中重写应用程序或更改为另一个RDBMS。逻辑和最简单的路由是IDS / 4GL，然而，当我向我的客户提到Linux或类似Unix的平台时，他们反应消极，并要求一个Windows平台，所以最简单的解决方案可能是4J，Querix等。或者Access，Visual FoxPro或??? ..任何人都有建议？

I have the following dilema: My clients (mom-n-pop pawnshops) have been using my mgmt. system, developed with ISQL, for over 20 years. Throughout these two decades, I have customized the app to each clients desire, or when changes in Laws/Regulations have required it. Most clients are single-user sites. Some have multiple stores, but have never wanted a distributed db, don't trust the reliability or security of the internet or any other type of networking. So, they all use Standard Engines. I've been able to work around some SE limitations and done some clever tricks with ISQL and SE, but sooner or later, new laws may require images of pawnshop customers, merchandise, electronic transmision, etc. and then it will be time to upgrade to IDS, re-write the app in 4GL or change to another RDBMS. The logical and easiest route would be IDS/4GL, however, when I mentioned Linux or Unix-like platforms to my clients, they reacted negatively and demanded a Windows platform, so the easiest solution could be 4Js, Querix, etc.?.. or Access, Visual FoxPro or ???.. anyone have suggestions?

推荐答案

看看 Aubit4GL - 也就是说，我相信，可用（或可以在Windows上编译）。

Look at Aubit4GL - that is, I believe, available (or can be compiled on) Windows.

是的，IDS正在为单用户系统过度使用，但如果SE不提供您需要的所有功能，或者预计在不久的将来需要，这是一个完全合理的选择。然而，对于少量的护理，其可以被设置为（基本上）对于用户完全不可见。对于像这样的非紧张应用，配置不复杂。作为供应商，你需要相当清楚。但是有一些功能，如静默安装，您可以让您自己的安装程序运行IDS安装程序，获得软件到客户的机器没有额外的东西。系统的总大小将增加 - IDS在磁盘上比SE大得多（但你得到更多的功能）。还有一些机制，去除更大的代码块，你不会使用 - 在所有的概率。例如，您可能使用ON-Tape进行备份;因此，您将从发送给客户的物品中省略ON-Bar和ISM。

Yes, IDS is verging on overkill for a single-user system, but if SE doesn't provide all the features you need, or anticipate needing in the near future, it is a perfectly sensible choice. However, with a modicum of care, it can be set up to be (essentially) completely invisible to the user. And for a non-stressful application like this, the configuration is not complicated. You, as the supplier, would need to be fairly savvy about it. But there are features like silent install such that you could have your own installer run the IDS installer to get the software onto the customer's machine without extra ado. The total size of the system would go up - IDS is a lot bigger on disk than SE is (but you get a lot more functionality). There are also mechanisms to strip out the bigger chunks of code that you won't be using - in all probability. For example, you'd probably use ON-Tape for the backups; you would therefore omit ON-Bar and ISM from what you ship to customers.

IDS用于没有用户且没有管理员使用系统的嵌入式系统。硬件位于橱柜（衣柜）中，通过网络进行通信。

IDS is used in embedded systems where there are no users and no managers working with the system. The hardware sits in the cupboard (closet) and works, communicating over the network.

这篇关于IDS对单用户应用程序的过度杀死？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！