I usually do 3 consecutive FIND's with a reasonable expectation of good results.
FIND BP PARTS then FIND BP WRITE then FIND BP 139 or 140 This assumes that the file PARTS isn't passed by an outside process, that the WRITES aren't performed with an old-school locking subroutine and that 139 or 140 are literal. Plus, theres so many indirect updates with variables that work but are hard to identify. This sort of goes back to my earlier request for a file analyzer that illustrates the READS, WRITES etc. Good luck. Mark Johnson ----- Original Message ----- From: "Bruce Ordway" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Friday, September 09, 2005 12:41 PM Subject: [U2] Tracking down how fields are filled > Hi, > > > In my INV Dictionary I found a custom item called Z_AVEUSE > with the following conversion: > > SUBR("-OCONVS",(SUBR("-OCONVS",F0,"TPARTS;X;;139")/SUBR("-OCONVS",F0,"TPARTS > ;X;;140")*365)+.049,"MD0") > > It seems to give good numbers back for part usage during a 12 month period. > I could easily make a report or Query Builder using this value if I could > trust it. > I wanted to see where it was getting it's values to make sure it's OK to > use. > > When I go to my PARTS dictionary F139 and F140 tuened out to be custom with > no documentation. > How could I find out when and with what these fields are getting written to? > > Thanks, > > Bruce Ordway > Viking Engineering > 763-586-1228 > [EMAIL PROTECTED] > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
