@br

[Kenneth Brody]

Quoting Jaime Perry (Fri, 03 Oct 2008 11:36:16 -0400):

> Thanks for the reply.  This sounds like I can't use it for what I want
> then.  To be more specific, I have a header/detail situation where I am
> showing the detail file in a browse.  I am trying to avoid putting a
> line number field in the detail file

Why?  How are you going to ensure that the order never changes unless you
explicitly tell it to change?

> but I still want line numbers in
> the browse for point of reference vs the total detail lines (real field
> line numbers would need to be recalculated when ever a record is added
> or deleted).
>
> I tried simply using a straight counter but that didn't work as
> expected.

I'm not sure how you expected it to work, but if you simply increment a
counter as you scroll through the records, consider what happens when the
user scrolls up.

>  It appears when using the retain position option in a
> browse,  and you have more detail lines than the screen holds, it
> doesn't redraw the browse from the top of the index, but starts at where
> the line is which changes 1,2,3,4.... to 19, 2,3,4,15....   I guess
> will need to add line numbers a code to reclac them when adding/deleting
> lines.

When does one delete line items from an existing invoice?  (Though I
suppose it may be possible that inserting lines in the middle of an
existing invoice might not be rare.)

-- 
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com