I should add that the missing "Global" information makes it impossible to decide if the current field is a "Global" field or a "Non-Global" field. Same FieldType is returned in both situations.
Interesting. Another way is to create a calculation and make it global (and text) and then script with one step of:
Show Custom Dialog [ FieldType ( Get ( FileName ) ; Get ( ActiveFieldName ) )
Place cursor in field and fire script. It says "StoredCalc Text Unindexed 1"
Globals, by their very nature, are unstored.
Yes. Basically it was the method I used. However, you will get the same result returned in this two situations:
(1) From a field defined as Global Calculation ContainerField and
(1) From a field defined as Non-Global Calculation ContainerField.
So a script - as an automatic process - can't from the result of FieldType determine, if current field is a global or non-global field in the 6 instances mentioned in my first posting. Only you - as a human being - might know, because you can visually inspect "Options" in "Manage Database for <Table>".
Thank you for your post.
I am able to replicate your results on both Mac OS X 10.6.5 and Windows XP.
I have forwarded your posts to our Development and Software Quality Assurance (Testing) departments for further review.