>>Yes it does update nqty, replaces nqty with nqty - qtyissued, which is why instock is included in the data environment.
>
>I thought this might be the case. The reason you don't see changes to the instock table in Form A is probably because you have buffering enabled on that table. The record in question is not refreshed until you do a TABLEUPDATE(). Therefore it's not a reliable source for the most current quantity value.

Dumb Questions about using a view
1. What is the advantage of a view over a cursor in the valid method?
2. If I use a view how do I create it when form is loaded?
3. Since testing is only in one place is there a reason for creating a custom method.

Opinion on my second problem, updating instock table. Other values are stored in a temp table (all records
are deleted when a new issue slip is started). Does storing new value for nqty there seem like a resonable
approch? This would seem to at least use latest value of nqty in my calculation.

>
>This is one reason why I like using views. You can have two views based on the instock table in Form A. One to look up quantity values whenever you need them and one for updating the nQty field. You only need buffering turned on the updatable view.
>
>>There are two problems I have with using private data session in this case. Both seem to be related to fact that orders form A does not see changes made by inventory maintenance form B.
>
>>1. Is the validation problem which could be solved by using a view
>>2. When updating the instock table the original value of nqty is used so that it results in negative values for nqty,