Quote:vReturnVal1 = @XLookupSourceList(@Fn,vPartNumber,"newprocs!NEWPROCS!DIACOM P\N", "ELASTOMER#;PFStatement2;PFStatement3;PFStatement4;PFStatement5")
writeln(vPartNumber,vReturnVal1)
I had struggled a beat in the past with @XLookupSourceList( ) command but it is such an efficient one that you are better off dealing with it instead of making endless @XLookup ( ) commands and opening up the lookup database that many times instead of just one time with @XLookupSourceList( ) command.
My experience tells me it is a problem with the string 99% of the time when simple @xlookup ( ) command is working with the same key value. The way I test the string is as follows:
vReturnVal1 = @XLookupSourceList(@Fn,vPartNumber,"NEWPROCS!DIACOM P\N", "ELASTOMER#") //;PFStatement2;PFStatement3;PFStatement4;PFStatement5")
WriteLN (vReturnVal1)
If that works fine, add one more to string and see..
vReturnVal1 = @XLookupSourceList(@Fn,vPartNumber,"NEWPROCS!DIACOM P\N", "ELASTOMER#;PFStatement2" )//;PFStatement3;PFStatement4;PFStatement5")
WriteLN (vReturnVal1)
If that works fine then...
vReturnVal1 = @XLookupSourceList(@Fn,vPartNumber,"NEWPROCS!DIACOM P\N", "ELASTOMER#;PFStatement2;PFStatement3") //;PFStatement4;PFStatement5")
WriteLN (vReturnVal1)
This way you will find the culprit in the string, the last added one is the culprit, check the spelling, semicolon, closing quotes, etc.