In FM7, you now have the option to make a field an "Auto Enter"

calculation that automatically updates, if you unselect the "Do not

replace the existing value of this field (if any)" checkbox.

So, what are the functional differences between an

Auto-enter Calc Field (replace existing contents)

and a

Calculation Field (Stored)

I understand the differences from a user-interface perspective (you

can't type into a Calc field).

But...are there any significant performance, speed, or size differences?

Both fields are stored, can be indexed, and can participate in

relationships, so it would seem that they should function more or less

the same.

In FM7, you now have the option to make a field an "Auto Enter"

calculation that automatically updates, if you unselect the "Do not

replace the existing value of this field (if any)" checkbox.

So, what are the functional differences between an

Auto-enter Calc Field (replace existing contents)

and a

Calculation Field (Stored)

I understand the differences from a user-interface perspective (you

can't type into a Calc field).

But...are there any significant performance, speed, or size differences?

Both fields are stored, can be indexed, and can participate in

relationships, so it would seem that they should function more or less

the same.

In FM7, you now have the option to make a field an "Auto Enter"

calculation that automatically updates, if you unselect the "Do not

replace the existing value of this field (if any)" checkbox.

So, what are the functional differences between an

Auto-enter Calc Field (replace existing contents)

and a

Calculation Field (Stored)

I understand the differences from a user-interface perspective (you

can't type into a Calc field).

But...are there any significant performance, speed, or size differences?

Both fields are stored, can be indexed, and can participate in

relationships, so it would seem that they should function more or less

the same.

In v6 Auto Enter calculation field you can editing manualy. But Calculation field you can not edit. May in v7 this difference are too?

In v6 Auto Enter calculation field you can editing manualy. But Calculation field you can not edit. May in v7 this difference are too?

In v6 Auto Enter calculation field you can editing manualy. But Calculation field you can not edit. May in v7 this difference are too?

Yes, same difference is in FM7.

However, in FM7 you can have the auto-enter calc be self-referencing, and automatically update itself after the user types in some data.

For example, you could create a phone # field

user types "800555122"

and the field reformats itself to

(800) 555-1212

This was not easily doable in FM6.

But I'm more interested in speed/performance/update issues... any ideas?

Yes, same difference is in FM7.

However, in FM7 you can have the auto-enter calc be self-referencing, and automatically update itself after the user types in some data.

For example, you could create a phone # field

user types "800555122"

and the field reformats itself to

(800) 555-1212

This was not easily doable in FM6.

But I'm more interested in speed/performance/update issues... any ideas?

Yes, same difference is in FM7.

However, in FM7 you can have the auto-enter calc be self-referencing, and automatically update itself after the user types in some data.

For example, you could create a phone # field

user types "800555122"

and the field reformats itself to

(800) 555-1212

This was not easily doable in FM6.

But I'm more interested in speed/performance/update issues... any ideas?

A key difference is that a calculation using a related, global, summary or unstored calculation field cannot be indexed, while an auto-enter field using the same calculation can be indexed. Indexing makes searching that field much faster.

A key difference is that a calculation using a related, global, summary or unstored calculation field cannot be indexed, while an auto-enter field using the same calculation can be indexed. Indexing makes searching that field much faster.

A key difference is that a calculation using a related, global, summary or unstored calculation field cannot be indexed, while an auto-enter field using the same calculation can be indexed. Indexing makes searching that field much faster.

I want to create a button the will select a checkbox, and go to a layout. (Not to dificult). The problem comes in when there are onther check boxes already selected. In this cae, the button (script) will select the box that I want and go to the layout, but it also deselects the previously checkd boxes.

Please help.

Use this to set your field:

Set Field [ MyField, MyField & "New Checkbox" ]

This will add your selection to whatever is already checked.