Any chance 'Type' is an undocumented restricted keyword?

I've created two forms, "Institutes" and "Orders". Think of Orders as organizations; Institutes as types of Organizations. The Institutes form has only one field, "Type". Its values are used when creating records in the form named "Orders" such that any value in entered in the Order's "Name" field also will have an associated "Type". To do this, as would be expected, a drop down list in the Orders form exists, named "Institute"; it is dynamically populated with all of the "Type" values found in the Institutes form. I abstracted the types of institutes in this way because because, as Institute choices grow, I would rather update the Institutes table than change the source code.

Everything was working fine. I was able to create a very large number of Orders, some 450 of them, each with a given Institute reference, about 10 or 12 of those in total.

Then I added a third form, named "Person." Most every "Name" in the "Person" form will also needs an associated "Order" value. Because there are so many Orders, I added another drop down list to the Person form, which I called "Institute". I wish to populate the drop down list called "Institute" on this "People" form with every "Type" found in the Institutes form and I want to limit the "Orders" drop down list to only those organizations that correspond to the currently selected Institute -- because that will limit by a great amount the number of entries present in the "Order" drop down list--down to something like 50 or 70 from 450. This should be easy enough to do because I had no problems doing something similar when creating the form which populated the "Order" table in the first place. But I am, in fact, encountering a strange error.

The following code snip describes the error. It is associated with the OnLoad() function of a radio selector called "Association" which is present on my "People" form. Only if Association is "X" does an reference to an Organization make sense for a "Person" in my application, therefore, if Association is not X, I clear the two drop downs and force them to "[not applicable]":

//Populate the order names as necessary if the association is of the right type
if (input.PersonAssociation != "X")
{
clear PersonInstitute;
clear PersonOrder;
PersonOrder.add("Select Type of Institution first...");
for each t in Institutes
{
PersonInstitute.add(t.Type);
}

//The code to initially populate the Orders drop down, which would
//go here, is not yet written

}
else
{
clear PersonInstitute;
clear PersonOrder;
PersonOrder.add("[not applicable]");
PersonInstitute.add("[not applicable]");
}

The problem is with the "PersonInstitute.add(t.Type)" call. When trying to save this script, I receive the message(s):

Encountered "." at line 9, column 30.
Was expecting one of: ")" ... "*" ... "/" ... "%" ... [blah, blah, blah]

So I returned to the Institutes form, added an unrequired text field called "X" (no correspondence with the radio choice described above) -- and did not populate any values in the existing data table -- and re-ran with one change to the script, changing out "PersonInstitute.add(t.Type)" for "PersonInstitute.add(t.X)". Now the save works without incident.

But, when I try to run the "Persons" form, I get an endless wait "looping circle". The Person form never loads, but if I select other forms, they do.

1. What's going on with "Type"? I could reference it in code for the "Order" form, but cannot in "Person" form.

2. And, now that the script associated with my "People" form can be saved by loading data (null values, admittedly) from field X, why does the form never load? Is it because these are null values? If so, how silly! Your form loader should, by default, convert nulls to single spaces for the purposes of display and subsequent processing, rather than run for 18 or 180 or 1800 hours without generating a comprehensible error. I've, of course, logged off and on, and all that. It makes no difference.

Thanks for your help.