Code/400 and CURLIB -- CODE400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Code/400 and CURLIB
From: "Jon Paris" <Jon.Paris@xxxxxxxxxxxxxx>
Date: Thu, 14 Feb 2002 16:42:55 -0500
Importance: Normal
List-archive: <http://archive.midrange.com/code400-l/>
List-help: <mailto:code400-l-request@midrange.com?subject=help>
List-id: CODE/400 Discussion & Support <code400-l.midrange.com>
List-post: <mailto:code400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/cgi-bin/listinfo/code400-l>,<mailto:code400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/code400-l>,<mailto:code400-l-request@midrange.com?subject=unsubscribe>

Hak,

all this talk about "fixing" current library issues has me a little
concerned.  I was assured some time ago that the Code/400 practice of
requiring a current library - in fact a current library _unique_ to the
user - was going to be done away with in the next release.  Please tell me
that is still true - I have encountered several customers where this
requirement makes the product virtually unusable without major changes to
their operating methods.  It was a dumb idea to begin with and really does
need to be fixed.

Jon Paris
Partner400

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.