I'm pulling my hair out trying to get an @XLookUpSourceList statement to work.  I've used them before but i don't understand why this one doesn't work!

See the programming below.

I'm trying to get a variable from the operator that I've assigned vPartNumber.  I can tell this is working with the writeln statements.  However, there is no data from the @XLookUpSourceList command.

I've attached a photo of the menu tree of my application for your info.

Any suggestions would be a big help.




Var vReturnVal1 as string
Var vPartNumber as string
Var i as Int
Var vOutputFile as String
Var vFileHandle as Int         
Var vData as String   
Var vNames as string      
var vPFStatement1 as string
var vPFStatement2 as string
var vPFStatement3 as string
var vPFStatement4 as string
var vPFStatement5 as string
var vPFStatement6 as string
var vPFStatement7 as string
var vPFStatement8 as string
var vPFStatement9 as string
var vPFStatement10 as string
var vPFStatement11 as string
var vPFStatement12 as string
var vPFStatement13 as string
var vPFStatement14 as string
var vPFStatement15 as string



Function CleanData(vData as String) as String

     vData = @Replace(vData, @Newline(), "  ")
     vData = @Replace(vData, @Chr(34), @Chr(39) + @Chr(39)  )
     vData = @Replace(vData, @Chr(255), "" )
     Return(vData)

END Function

// GET DC NUMBER FROM THE OPERATOR
     
vPartNumber=@PromptForUserInput("PLEASE ENTER A DC NUMBER.","")

writeln("XX";vPartNumber;"XX")

// GET INFO FROM WORK INSTRUCTION FILE


vReturnVal1 = @XLookupSourceList(@Fn,vPartNumber,"newprocs!NEWPROCS!DIACOM P\N", "ELASTOMER#;PFStatement2;PFStatement3;PFStatement4;PFStatement5")

writeln(vPartNumber,vReturnVal1)

vPFStatement1 = @AccessStringArray (vreturnVal1, 1)
vPFStatement2 = @AccessStringArray (vreturnVal1, 2)
vPFStatement3 = @AccessStringArray (vreturnVal1, 3)
vPFStatement4 = @AccessStringArray (vreturnVal1, 4)
vPFStatement5 = @AccessStringArray (vreturnVal1, 5)

//PFStatement15 = @AccessStringArray (vreturnVal1, 15)



WriteLN(">>>> ";vPFStatement1, vPFStatement2,vPFStatement3,vPFStatement4,vPFStatement5)

Thanks, but I tried that already and it didn't work either.  Is my variable the problem?

Quote:


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.

Erika asked if all element names are spelled correctly, you may want to check for any spaces after your element names. This is how it happens to me, I sometimes adjust the label with spaces to move the text further away from the field, I should be doing this in the Property Editors Label field. For whatever reason, I’m not paying attention and do it in the Property Editors Name field instead, adding unwanted spaces for the name. Not giving it another thought, I don’t go back and remove the spaces, that’s when @XLookupSourceList( ) stops working.

Outstanding code Bharat, I just ran it on mass update for one record, it does show the extra space, if any, in the field name!

Great tool!

Thanks for this, and have a great day!

Brandon