I wasn't clear about that at all, sorry. What I meant was that experienced developers don't put a table of 50,000 invoice numbers into a single attribute in the customer master file, or even reserve one atb for open invoices and another one for closed, especially when either one of those atb's can expend beyond a couple thousand values.
Equating a name to a dimensioned array element is absolutely standard and IMO preferred practice - sorry if that was confused. Tony Les Hewkin wrote: > Rubbish,sorry Tony but that's what I think. You say > experienced developers and big companies don't use "EQU > INVNO.TABLE TO CUST(40)". I beg to differ. What do you > call experienced? does 20 years count??? and what do you > call a big company??? we only have two boxes running > universe, two HP boxes, one with 32 processors and four > logical machines, with over 5k users. We define all our > files this way. Our user base is growing all the time as > the company grows and our apps just keep on working. > > Les. > > -----Original Message----- > From: Tony Gravagno > That construct that you > describe "EQU INVNO.TABLE TO CUST(40)" is something that > experienced developers simply don't use anymore... ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
