The code should be:

IF @add and TLItemNum <> "" then
     {
	     XLOOKUP (@FN, TLItemNum, "INVENTORY!ItemNum", "ItemDesc", TLItemDesc)
     }

 

remove quotes from arround TLItemNum.

Hello,

Please run the following two lines of programming in the On Element Exit event. If they do not display numbers greater than 0 in the Sesame Slate, then the element names do not exist in the external database.

Writeln(@CountStringArray(@XListValues(@FN, "INVENTORY!ItemNum")))
Writeln("==========================")
Writeln(@CountStringArray(@XListValues(@FN, "INVENTORY!TLItemDesc")))

Ben,
        nothing but '0'.    I have dbl-checked the element names in the Inventory db, and they are ItemNum (text field) and ItemDesc (text field).

Bharat,

When I load the application, I get an error that says "Some or all of the programming in this form has  failed to compile.  No event programming will run"

I go to preview app, and when I enter an ItemNum and exit that field, I get the following message: "Error:  A runtime SBASIC error has ocurred.  Please close this form and repair the condition before continuing"

Bharat,

your code resulted in a blank Sesame Slate popup window


I'll post my code and database.    By the way, should the ItemNum and ItemDesc fields in Inventory (the Source database) be 'bound' ?

Bharat,

//Trucks.db, with TruckLines.db as a subform of the Trucks.db
//Inventory.db  
     A dispatcher needs to build a picklist of products to load onto a delivery van.  So they create a new record in Trucks, and enter the items that need to be picked in the subform TruckLines.  I want him to input the ItemNum, and then have the programming find the matching ItemNum in Inventory.db and have the product description pulled from the Inventory!ItemDesc field and plugged into the ItemDesc field on the TruckLines subform (sales reps navigate with part #'s, but delivery drivers usually rely on the description field of the item).

//code (on element exit, entered on TLItemNum)

IF @add and TLItemNum <> "" then
     
{
     XLOOKUP (@fn, TLItemNum, "INVENTORY!ItemNum", "ItemDesc", TLItemDesc)
}


fyi, here is the programming I have in my QA Trucks database (STOCK = Inventory.db, and "PART #" = ItemNum) ...
>#50: XLOOKUP ("STOCK",#50,"PART #","DESC.",#51,"LOCATION",#52); GOTO #11

no security yet.

The elements are not bound at the present time.  Do I need to do so?

lksseven,
If the element in the Layout is not bound to the field of the underlying database that means it does not store any value in the database. Such unbound text elements are used to display the calculated value that does not required to be stored.

Also note that there are new terms when you come from Q&A background that you should be very clear about, such as

Application
Database
Field
Layout
Element

All these terms have distinct meanings.

Bharat,

I appreciate your help!!!!!

so my application, wc2.db, is comprised of the following databases:
Client
Inventory
Orders (subform SOLines)
Purch (subform POLines)
Pricing
Vendors
Trucks (subform TruckLines).

so if I want to have TruckLines (subform to Trucks) pull from Inventory!ItemDesc, should the Xlookup programming begin (@fn .....  ?
        

btw, I have bound those fields, and still no joy.

Obviously I have miles to go.  I promise I won't be this wordy/needy after I get past 2+2=4 

it worked.   Unlocking the wc2.db and then binding the fields to the elements, and then re-entering the programming worked.

Sorry for my brickhead - I feel like a raw recruit on the first day of rifle training (hey, Sarg, what's this thing do?   "Bang!" )

Bharat, I still don't understand the drawback of using xlookup to pull in the ItemDesc that accompanies ItemNum.

I will read up on @FormFieldValue this evening.

Have a great evening!

Thanks, Ben!

Bharat,  your advice was put to good use - I was studying up on FormFieldValue last night and have a much better understanding of it now.  Thanks for the pointer.