Where are you trying to run the script from? oBusObj points to something entirely different depending on where you are running the script.

I can see plenty of things that need to be fixed in the script, but knowing exactly where the script is executing from makes a big difference.

they are on 2016 advanced and access via TS through RDP. I really appreciate your help. I could spend hours paying with scripting, its pretty fun! But I do not have hours to play around this time :)

I think you may mean my table for my UDF BM Bill of Materials Detail

My question would be: why do this (since reports can link back to the source), but...
Get the component item code from the bill detail, open CI_Item for that item and grab the key, then do your lookup for the extended description text.

the need to see the extended item on the component in the bill detail.. I am not sure I understand what you mean..

This line skips a few steps, which I described at a high level.
rv = oBusObj.GetValue("ItemCode$", ExtendedDescriptionKey)

I tried it and I still get nothing...I must be doing something wrong

Put message box pop-ups in your script to walk through the values as you step through the process.

First off, this is line

rv = oBusObj.GetValue("ItemCode$", ExtendedDescriptionKey)

is getting the ItemCode from the BM_BillDetail file NOT the Extended Description Key.


Use the value from this to look up the CI_Item record first.

Once you have that CI_Item record you can get the Extended Description Key from that record to look up what you need in the CI_Extended Description file.

(Actually, there is no field called "ItemCode" in BM_BillDetail, so that line is getting nothing).