×

Good News Everybody!

The new search engine is LIVE!

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




Alan,

What would be the problem with simply reading the 5400247 record, saving its
details, deleting it, reading the 1 record and updating it with the details
from the 5400247 record? Simply define the file as update-capable in the
F-specs.

Seems a lot simpler to me and you wouldn't need all this duplicate-file
stuff.

Rory

On Tue, Nov 17, 2009 at 12:58 PM, Alan Shore <AlanShore@xxxxxxxx> wrote:


Thanks for your reply Booth
Maybe the choice of the word key was the wrong choice
Here is my example
the key to the customer file is by customer number
2 records exist the customer file
customer number 1
customer number 5,400,247
They are in fact the same person, so we need to "merge" the data from
customer number 5,400,247 into customer number 1
Update customer number 1
delete customer number 5,400,247

I think it would be easier (maintenance wise) to have 2 separate files,
both keyed by customer number. One file is to update. The other file is to
delete
Is this fool proof - no, but in the long run, it will be simpler (my
opinion for what its worth)



Alan Shore
Programmer/Analyst, Distribution
E:AShore@xxxxxxxxxxx <E%3AAShore@xxxxxxxxxxx>
P:(631) 200-5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill


As an Amazon Associate we earn from qualifying purchases.

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.