remembering the amount

[John]

Hello. Have a mainform (purchase orders) with a tab control on it.
The second tab page has a subform on it (the purchase order details).
A field on the subform footer totals up the cost of the details line
items. On the mainform is another field that shows what the subform
total is (subtotal). Neither of these field's amts are stored
anyplace, they are calculated unbound fields.
All the users have a po dollar limit. Anything over this limit they
need to get it approved. The subtotal field on the mainform is what
'triggers' this approval process. The subtotal field changes anytime
the detail items goes up or down. If the amt goes up due to adding
more line items, change qty of line items, or the price of the line
items, it triggers another approval process. But, once it is
approved, should the amt go down (possible removal of a line item,
price change, etc), the user does not need to go thru the approval
process again. So if a user originally purchased $5000 and in the
subtotal at approval time then reduced the line items to $4000,
approval not needed as it is less than the approved $5000. It is
possible that the user could modify the line items the next day after
it was approved.
Where and how would the $5000 be tracked/captured? This has me
stumped.
Thanks for reviewing.
John

 

[Mike Painter]

The main/header table is probably the best place to store an approved
amount.
At some point you might have to add a related table that kept notes on that
amount.
7/12 $2.99 limit approved by MP
7/15 raised to $3.01 and approveved by the moose.

 

[John]

The main/header table is probably the best place to store an approved
amount.
At some point you might have to add a related table that kept notes on that
amount.
7/12 $2.99 limit approved by MP
7/15 raised to $3.01 and approveved by the moose.




- Show quoted text -

I was wondering if I should add the unbound field to the po table.
Then when the approver approves the po (button event) then insert the
amt into the table. Since the field is unbound, the amt won't change
if the details do. Should the details go above the approved amt, it
would trigger the approval process over again, thus establishing a new
threshold amt.
Thanks for reviewing and the idea.
John

 

[Mike Painter]

I was wondering if I should add the unbound field to the po table.
Then when the approver approves the po (button event) then insert the
amt into the table. Since the field is unbound, the amt won't change
if the details do. Should the details go above the approved amt, it
would trigger the approval process over again, thus establishing a new
threshold amt.
Thanks for reviewing and the idea.
John

That just requires an extra step and you will be doinf what Access does
automatically.