Question on Header-Detail programming.

[Richard Kreiss]

> -----Original Message-----
> From: filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com
[mailto:filepro-
> list-bounces+rkreiss=verizon.net at lists.celestial.com] On Behalf Of Boaz
> Bezborodko
> Sent: Tuesday, December 22, 2009 9:47 AM
> To: filepro-list at lists.celestial.com
> Subject: Question on Header-Detail programming.
> 
> I've programmed a few Header-Detail applications where I used a set of
> line-numbers for the detail, but each set of line-numbers starts with
> 1.  The uniqueness of each detail is based on the combination of the
> header number (say invoice number or order number) and the line number.
> I was watching John's Survivor Series where he says to use a unique
> number for each detail record.
> 
> 
> What is the advantages/disadvantages of using his method versus the way
> I've used them in the past?
> 

I have used your method of numbering each detail line entered.  I would say
that the combination of order/invoice + line number is unique.

Numbering the details allows for the them to be displayed in the order in
which they were entered or created.  This make matching details to vouchers
or order details easier.  I have one application which gives the clerk the
option of displaying in a browse the order details as entered or by item #
or by descriptions. 

I have not looked at that in John's survivor series but will take a look at
it.


Richard Kreiss
GCC Consulting
rkreiss at gccconsulting.net