×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




Jeff,

Why do you delete all the records of the group? Why don't you just update?

What I do in situations like is to store the original sequence # as a hidden field in the subfile. With the original and new sequence # you can determine what to do:
- original = 0 and new > 0: add
- original > 0 and new = 0: delete
- original <> new: update

The tricky bit is checking for duplicates. You need to check each new/changed sequence # with the file and also check for duplicates within the subfile.

Joep Beckeringh


Jeff Young schreef:
Let me clarify what I am attempting to do.
I have a file with the key: Company, Location, Item, Seq#, Substitute Item.
The file has additional fields.
The user sees all substitute items for the Company, Location, Item and can change the Sequence # and other data shown.
Since the user can change the sequence #, I need to process all records for the group.
When I do the update/add, I need to resequence the data on file based on the seq# the user keyed.

This is similar to what is done in SEU when you insert or delete lines.

What I am doing now is storing the screen seq# & substitute item in an array, sorting the array and then deleting all records for the group.
When I output the records from the subfile, I assign a sequence # based on the location of the seq#/item in the array.

I was hoping for a less messy method to get the same result.

Thanks,
Jeff Young Sr. Programmer Analyst
IBM -e(logo) server Certified Systems Exper - iSeries Technical Solutions V5R2 IBM Certified Specialist- e(logo) server i5Series Technical Solutions Designer V5R3
IBM Certified Specialist- e(logo)server i5Series Technical Solutions Implementer V5R3


This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 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.