Parent "Purch", subform "POLines" .  When placing PO's (which consist of multiple line items ordered on the same PO to a vendor), I would like to have POLines!ItemCost  posted to the Inventory!ItemCurrentCost  field as each line item is placed with the vendor and the current cost confirmed.  So that any sales orders or quotes or pricing updates done subsequently during the day gets the benefit of up-to-the-minute cost info.

I have a field in my POLines subform - POLinesYN, which is a yes/no field.  When the line item is placed with the vendor, I enter a "Y" in this field to show that the line item was not only intended to be ordered, but has in fact been ordered.  My thinking was that 'on element change' would be the trigger that fired the XPOST.  Is this a good idea, or should I approach this a different way?

Here is my attemped code which is not working
if ((@Mode() = 1) or (@Mode() = 0)) and (@isBlank(POLinesYN) = 0)
           {
                 XPOST(@fn, ItemNum, "Inventory!ItemNum", ItemCost, "Inventory!ItemCurrentCost", "")
           }

Hi Bharat,

Yes, I've been studying the XResultSetValue command, but am having a little trouble with the syntax.   My thinking was that I'd tryout the XPOST command (since I'm more Q&A familiar with the 'Post' concept) on a few practice records just to make sure I had the concept down pat between the fields of the two databases (POLines!ItemCost and Inventory!ItemCurrentCost). Once I got that to work, then I would start experimenting with XRSV and implement it in subsequent code.   But I can't get the POLines!ItemCost to post/replace the Inventory!ItemCurrentCost.  I'll keep at it.

thanks Bob!  I'll give it a try right now (on my way to lunch, but this is worth a few bites of tuna!)

How are you triggering the XPOST oommand?

XPOST(@fn, ItemNum, "Inventory!ItemNum", ItemCost, "ItemCurrentCost", "")  should take the ItemCost value from the current record and place it into the ItemCurrentCost element in the InventoryItem database where the ItemNum value matches the ItemNum value of this record.  Make sure that both databases have the same data types for the matching elements.

This should work on every record in a Mass Update
It should work on each record if OnFormExit which is where I would probably put it.  It should be followed with commands for error checking.


Here is an approach(put in some WriteLn commands to show results):
You can get the existing value from external record before doing XPOST
Then do the XPOST
Run @ERROR command, and continue if OK
Then get the current value from external record after XPOST and confirm math/replacement was done correctly ELSE some type of Error Response programming.

Glad to hear you are working OK.

But, remember to look at the xResultSetValue ( ) command.

Remember, you don't need to delete code in development.  You can comment out blocks of code (XPost) and try the new code (XRSV), if not working yet, then just comment out the XRSV and uncomment the XPOST to keep working.  This will allow you to pick away at new code, but still have working code for current operations.

I am having trouble following how to use XresultSet commands to replace XPost where I am adding or subtracting from the field I am posting to. the way I see it it requires 3 commands. One to retrieve the value, one to perform the operation and one to save it.
Am I missing something?
Harley

Thanks Bob,
Think I'll stick with my 3 statements using @XResultSetValue, math, XResultSetValue.