Remote transform calculation fields into regural fields.

[edudna]

I wonder if we can transform calculation fields into regural edit fields by a button or anything else. This will help the users to by-pass automatic processes and complete the fields of their own. It is very usfull in cases that user or client already know time or expenses and does not want to complete fields in order to get a known result.

Pascal

[Lee Smith]

Instead of using a calculation field, use a Text field (or same type as the Calculation Result), and then use the Auto Enter

Select your Calculation Field

Select Field Options

Auto Enter >> Calculated Value and the the calculation you were using. (Note: the calculation field should show in the box if you are converting it).

Click Okay,

and [color:red]Deselect the "[color:blue]Do not replace existing value in field (if any)

Click Okay

HTH

Lee

[edudna]

Thank you Lee

and

Have a good day.

Works fine for some fields but not for others why is this happen?

Pascal

Edited January 30, 2007 by Guest

[edudna]

I have tried this autocalculation but it does not work for some fields. I used this in a portal. The problem is that when calculates based on a summary field it shows the results only of the first record and not the results of the last records of the related table. I hope you can understand. Otherwise I put an example.

Pascal

[Lee Smith]

autowhat?

Yes, post a file and explain the steps you are going through and what you expect to happen and what isn't working.

Lee

[edudna]

Thank you for your response again,

Lee

Here is an example file. Summary and Summary_expression fields work differently in a portal than summary or calculation fields. You should convert the two mentioned fields to autocalculate fields (text) as you describe to justify this.

test_dates.zip

[Søren Dyhr]

You better start wonder why we have this:

http://www.filemaker.com/help/FunctionsRef-341.html

And especially what is said about aggregate functions - you can not use summary fields and rely on them execpt in the header or footer area in browsemode, but you could utilize this principle instead if the use of aggregate functions are too slow to await rendering:

http://www.filemakerpros.com/PORTFILL.zip

Nowhere in the documentation could your use of summary fields be justified. Use instead Sum( over the relation!

--sd