Two Global Calc bugs

Using FM Server 7v3, I find two very serious bugs. Can anyone else confirm?

Bug #1

Make a global calculation field equal to a text constant, i.e.

kgKey1 = "Work" (calculation, global storage)

Add the field to a layout and verify that the field has the right value.

Now, go to table definition, duplicate the field definition, and change it, i.e.

kgKey2 = "Home" (calculation, global storage)

Add the field to your layout.

Notice that the field will not have the correct value. You must re-open the database for the global field to refresh to the correct value.

Bug #2

Global calcs that reference a summary on a self-relation hangs filemaker server.

Create a table with a self-Cartesian relation (i.e. the "X" operator). Put about 20,000 records in it.

Create a calculation with global storage that references this relation , i.e.

gcMaximumSerialNumber = Max(SelfRelation::Serial) (calculation, global storage)

Save changes. (sometimes you need to edit it again to see the bug)

At this point, Filemaker Server will go to 100% CPU, and stay there forever, even if you force-quit FileMaker Client. It appears to me that it either gets in an infinite loop, or perhaps it is trying (incorrectly) to evaluate the Max(SelfRelation::Serial) calculation for EVERY RECORD (even though this is a global calculation, which means it should only have to evaluate it once).

Beware global calculation fields!