I'd all the shaired objects such as subforms and shaired fields have name spaces.
For example, supose your designing an invoice system. An invoice may have three different addresses: the ordering address, the billing address and the shipping address. I want to create a subform the has all the fields and validation stuff I need for an address. Call it ADDRESS.
Then, each time I add it to my form Designer would prompt me for an name-space name. I'd add it three times with ORDERING, BILLING and SHIPPING as the name-space name.
Each field in the subform would have the name-space name as aqualifer to its original name. I could then write code to access fields like
BILLING.StreetAddress
ORDERING.StreetAddress
SHIPPING.StreetAddress
The original Notes was designed before the Object Orentation craze, but they came just so close, so very close to being an object-store.
I'd all the shaired objects such as subforms and shaired fields have name spaces.
For example, supose your designing an invoice system. An invoice may have three different addresses: the ordering address, the billing address and the shipping address. I want to create a subform the has all the fields and validation stuff I need for an address. Call it ADDRESS.
Then, each time I add it to my form Designer would prompt me for an name-space name. I'd add it three times with ORDERING, BILLING and SHIPPING as the name-space name.
Each field in the subform would have the name-space name as aqualifer to its original name. I could then write code to access fields like
BILLING.StreetAddress
ORDERING.StreetAddress
SHIPPING.StreetAddress
The original Notes was designed before the Object Orentation craze, but they came just so close, so very close to being an object-store.