Even if you stay with the 'old' SCAN command, you should use all its
possibilities (capabilities ?) :
SELECT EDIHDR SCAN FOR SEEK('TARGE'+edihdr.CUSTPO, 'orderhdr')
SELECT OrderHdr
* if you had a good index, you could have a fine SCAN REST WHILE a lot
quicker
* than the SCAN REST FOR
SCAN REST FOR account+custpo+order = 'TARGE'+edihdr.CUSTPO
SELECT EDILN
SCAN FOR ORDER+STYLE+COLOR+STORE= OrderHdr.order ;
AND !EMPTY(mstrupcno) AND ;
SEEK(OrderHdr.order+EDILN.STYLE+ EDILN.COLOR+EDILN.STORE,
"orderln") ;
AND EMPTY(xxxx.mstrupcno)
SELECT OrderLn
REPLACE mstrupcno WITH EDILN.MstrUpcNo , ;
MstrUpcQty WITH EDILN.MstrUpcQty, ;
MstrUpcPrc WITH EDILN.MstrUpcPrc
ENDIF
ENDSCAN
ENDSCAN
ENDSCAN
I haven't test it and there is a logical problem with EMPTY(mstrupcno)
The Foxil
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
