I've done this before:

In this example, you'll set the value of sGL to be the GL Account you want to find.  The value of sGL may or may not need to be padded (sGL = sGL & "00")

If sGL <> "" Then '3

Set oGL = oSession.AsObject(oSession.GetObject("GL_Account_svc"))

sGL = sGL & "00"
retVal = oGL.SetIndex("kRAWACCOUNT")
retVal = oGL.Find(sGL)

if retval = 1 then '4
retval = oGL.GetValue("AccountKey$", sGLKey)
End if '4

retval = oBusObj.SetValue("SalesAcctKey$", sGLKey)
End If '3

Instead of looking up the GL Account Key you can just use the fully formatted account G/L Account Number in the SetValue() into the business object.

Try:  oLines'SetValue("SalesAcctKey$","100-30","kACCOUNT")

You would add the third argument which is the secondary key to validate against.  In this case "kACCOUNT".  The result will be SalesAcctKey$ will be set to the GL Account Key for GL code 100-30.

I never knew that!  Is this new?  I wrote that script years ago on an older version.  I never saw this in any of the documentation for scripting.  That's much easier!

Simple and elegant solution.   Thank you for the help!

And thanks to hyanaga for looking into it as well.

This is special to G/L Accounts hyanaga.  :)