× 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: Re: PDM Library List
  • From: "OleBlighty" <oleblighty@xxxxxxxx>
  • Date: Wed, 2 Feb 2000 17:34:18 -0800

----- Original Message -----
From: Reger, Bill <breger@levitz.com>
To: <MIDRANGE-L@midrange.com>
Sent: Wednesday, February 02, 2000 1:38 PM
Subject: RE: PDM Library List


> I respectfully suggest that your problem isn't in how to submit your
> compiles but in your method of operation.  I think it makes much more
sense
> for you to have the production libraries in your library list, with your
> development libraries above them.  This facilitates not only your compiles
> and object creations, but it also gives you a good library list for
> subsequent testing.
>
> William K. Reger

Call me old fashioned, or maybe I am missing the point...but...doesn't that
approach leave the door open for possible production database corruption.
Shouldn't the correct method be, given dev and prod on the same box and
enough disk, to have completely separate library lists for dev and prod.


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.