× 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: "Reger, Bill" <breger@xxxxxxxxxx>
  • Date: Wed, 2 Feb 2000 23:08:14 -0500

I should have mentioned that this assumes that developers are given
"read-only" access to production libraries and "all-authority" to
development libraries.  This is the structure we have used here since the
beginning of time and we've never had a problem.  Works great!

William K. Reger
Senior Project Manager
Levitz Furniture Corporation
Phone:  (561) 994-5114
E-mail:  breger@levitz.com


> -----Original Message-----
> From: OleBlighty [mailto:oleblighty@home.com]
> Sent: Wednesday, February 02, 2000 8:34 PM
> To:   MIDRANGE-L@midrange.com
> Subject:      Re: PDM Library List
> 
> ----- 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
> +---
> 
+---
| 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 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.