× 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.



Hi Buck,

Here's a point of confusion -- if an AG is a subdivision of a job, then why
is it necessary to avoid naming conflicts with AG's in other applications
when using NAG's?

Peter Dow
Dow Software Services, Inc.
909 425-0194 voice
909 425-0196 fax



----- Original Message -----
From: "Buck Calabro" <Buck.Calabro@commsoft.net>
Sent: Monday, March 11, 2002 8:09 AM
Subject: RE: Activation groups for beginners
> I've been calling a Named Activation Group a NAG.  The only difference
> between a NAG and *NEW is who assigns the name.  With a NAG, the
programmer
> is responsible to see that the chosen name is appropriate (that it won't
> clash with other applications).  With *NEW there can never be a name
> collision; the system will assign a unique name every time.



_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.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.