No Brainer (Me or the Question?)

[John Gamble]

Should be simple enough.

On a form I have 2 calculators to help the user determine discounts & markups.

Works sometimes when adding a record but not always or when changing.

Re-Calc button calls for a "REFRESH" (Action Script). Help indicates this DOES NOT work in change or edit mode. Unfortunately the help fails to say what will work!

Simply, the re-calc button should force the form calculated fields to re-calc & display.

I never cease to be amazed at how the simpleset things screw up the works.

Thanks , John

[MikeC]

Re: No Brainer (Me or the Question?)

Hi John,

Help indicates this DOES NOT work in change or edit mode.

To place in "view" mode use a topparent.commit(). You could even check the mode first to eliminate the overhead of committing when not necessary.

Something like:

if tbl.mode_get()= 1 .OR. tbl.mode_get()= 2 then      'in change or enter mode
   topparent.commit()  'places in view mode
end if

[Stan Mathews]

Re: No Brainer (Me or the Question?)

What do the field objects shown on your form represent? A mixture of table fields and variables? What are the calculations done? Are they tied to events such as ondepart for the fields?

[John Gamble]

Re: No Brainer (Me or the Question?)

Stan

Calculator 1:

Standard Cost: Calculated (Field Rules) Reg. Cost - Disc %) .
Trial Markup: Variable - user enter
Trial List: Form calculated field: Std. Cost x Trial Markup.
Margin: Form calculated field: Trail List - Std. Cost.

Example:

Std. Cost: 50.00
Enter Trial Markup: 1.5
Trial List: 75.00
Margin: 25.00

The idea is that the user may repetitively try different "Trial Markups" (Calc 1)
or different Trial Discounts (Calc 2) until satisfied with the numbers.
Calc 2 the same but different.

Not tied to any events (what, you think I know what I'm doing?)

Thanks, John

[Peter.Greulich]

Re: No Brainer (Me or the Question?)

John,

You might try using variables only on the form, with the button's OnPush event with the code. Then a save button to write the vars to a table (if that is what you want) when the user has the results they are looking for.

[John Gamble]

Re: No Brainer (Me or the Question?)

Peter

Sounds like a lot of work. Stan's question about on depart twigs the question, is there a command that could be placed in the on depart event , that would simply force the calc fields to re-calc.

Sorry to seem so dense (always use A5 defaults & action scripting)

Contrary to popular opinion, Laziness not necessity is the mother of invention.
My story & I'm sticking to it.

Thanks, John

[Stan Mathews]

Re: No Brainer (Me or the Question?)

If memory serves, form level calculated fields should recalculate when any of the values involved in their expression definintion change. The only time you should need a commit and a refresh or resynch is if you are changing table level fields form representation. IOW, changing the value in a form object without saving the record does not change the table field value and thus calculations based on them do not re-calc.

[John Gamble]

Re: No Brainer (Me or the Question?)

Stan

Getting closer. By your definition the form calculated fields will not re-calculate when an "ENTER Trial Markup" is inputted, because it is a variable.

Would putting the "correct" command (refresh, resync....?) in the on depart event of this field force a re-calc.

Thanks, John

[Peter.Greulich]

Re: No Brainer (Me or the Question?)

Would putting the "correct" command (refresh, resync....?) in the on depart event of this field force a re-calc.

A refresh() or resynch() command will not force a calc update as far as I know. Those commands update underlying data tied to a form.

But try the following in your OnDepart event:

tbl = table.current()

tbl.recalc_calcFields()

[Stan Mathews]

Re: No Brainer (Me or the Question?)

I tried to recreate the first scenario and my form displays the trial list and trial margin changes immediately upon exiting the trial markup variable field. I did make my expressions for the form calculated fields a bit different.

Standard_Cost: Calculated (Field Rules) Reg. Cost - Disc %) .
Trial_Markup: Variable - user enter
Trial List: Form calculated field: Standard_Cost x var->Trial_Markup.
Margin: Form calculated field: calc->Trial List - Standard_Cost

[John Gamble]

Re: No Brainer (Me or the Question?)

Peter

Worked but takes 10 seconds to calc. Seems ridiculous as there are only 20 form calc field in total (3 of which are lookups).

Sounds like we are on the right track.

Will try to fiqure out how to place only the required calc's in the on depart event.

Thanks, John

[Stan Mathews]

Re: No Brainer (Me or the Question?)

Worked but takes 10 seconds to calc. Seems ridiculous as there are only 20 form calc field in total (3 of which are lookups).

tbl.recalc_calcFields() recalculates the table level calculated fields for every record in the table.

[Peter.Greulich]

Re: No Brainer (Me or the Question?)

tbl.recalc_calcFields() recalculates the table level calculated fields for every record in the table.

Ouch!

[John Gamble]

Re: No Brainer (Me or the Question?)

Peter, Stan, Mike

By moving only the required calcs to the on depart event,

WORKS, Instantly:D.

Thank you all.

Aside

A5 is again creating duplicate form calc fields, some the same, some different.

Deleting them does not work. They just pop up again.

????????

Thanks mucho, John

[G Gabriel]

Re: No Brainer (Me or the Question?)

Contrary to popular opinion, Laziness not necessity is the mother of invention.

Hey..hey..execuse me but that's my saying!

I ain't talking no more cause am hopping mad now!
And why do you even have to do any of that when there is a more sofisticated less time consuming approach?
But I ain't talking..