Re: design issue and /copy statements

[James Rich <james@xxxxxxxxxxx>]

Booth Martin wrote:
> Lets say, for discussion, that there were three procedures, totally
> unrelated, but that all three are used in many many programs.  For example:
>
> 1)Look up customer name and address info
> 2)check quantity on hand of an item
> 3)validate a credit card number
>
> When I write a program and retrieve these with a /copy, should I have one
> /copy or three /copy statements?

I would use three since (as you said) they are unrelated.  You will 
certainly in the future have more functions (subprocedures) that are 
related to these three.  Those you could group as customer info, 
inventory, and financial.  You would have three /copy members for each 
of these groups.  Put related things together in one /copy member and 
leave unrelated things seperate.  How you determine what is and isn't 
related is up to you.

James Rich