Find / Replace inside calculation fields

Can I do Find / Replace inside calculation fields?
I think this is a must have for me (for everyone too). If I change a relation name and that relation is used inside many calculations, then I would be able to do a global find/replace within calculation fields as well.

Thanks
Hameed

sounds like a great idea.

in general, editing of calculations is a little strange; it
would be great if they could just be opened and edited
in the method editor along with all global & form methods.

both (better search/replace and opening calculations in the method editor) are in the feature db’s. Don’t know exactly what release they will emerge.

excellent!

and now one more idea…(i’m full of ideas some days :lol: );

would it be possible to debug calculations?

RobertMeyer:
excellent!

and now one more idea…(i’m full of ideas some days :lol: );

would it be possible to debug calculations?

Yes, would be wonderfull

This is an excellent thing!!

Also it would be much better, if we can be able to find the fields placed in forms (find this by its dataprovider & element name) and labels placed in forms.

Thanks

jcompagner:
both (better search/replace and opening calculations in the method editor) are in the feature db’s.

Great :!:

jcompagner:
Don’t know exactly what release they will emerge.

:cry:

RobertMeyer:
would it be possible to debug calculations?

PPPPlease :!:

TIP: Great way to debug calculations: create a method that sets a global (or show a dialog) with the result of the calculation. This way you can use the debugger. Once debugged, copy/paste into your calculation (minus the global setting or showDialog). I do this all the time (I have a special “_aTEST” method for this purpose. WORKS!

Cheers,

Bob Cusick

but this doesn’t let you actually debug (step thru, and examine
variables in) the calculation, does it?

a trick i use a lot is to put “application.output()” statements
in the calcs to dump info as i’m debugging.

you can debug a calculation if you really want it.
Just make a global method where you move the code of the calculation for a while.
Then call that global method in that calculation (return globals.testCalcMethod():wink:

Set the breakpoint in the global method.

sounds good! thanks.