distinguishing a table field

[dunbarx]

Anyone ever need to determine whether a particular field is a table field?

There is a property in the inspector called "basicTableObject", but this is not in the dictionary, and asking for the value of that property makes LC think it is a custom property (the property is always empty).

Most fields that start out as ordinary fields have properties different from a plain vanilla table field, but those are all changeable, and therefore not reliable.

In other words, why is an explicit settable property in the inspector not in LC at all?

Craig

[Klaus]

Hi Craig,

looks like this checkbox only sets -> the cRevGeneral["table"] of that field to TRUE resp. FALSE, which LC obviously uses to distinguishing a table field.

That's why this is no LC property and thus not in the dictionary.


Best

Klaus

[dunbarx]

Klaus.

Ah, thanks.

So the answer to my question is:

Code: Select all

answer the cRevGeneral["table"] of fld 1

This harkens back to a thread I created a while back, where the "CRevGeneral" custom property is sort of invisible until it is used. I will try to find that thread, and see if I can drill into my head when and where is can and should be used, or at least examined.

Craig

[Klaus]

So the answer to my question is:

Code: Select all

answer the cRevGeneral["table"] of fld 1

Yes.

There is a property in the inspector called "basicTableObject", but this is not in the dictionary

To be precise:
That is no property in the inspector, just a simple checkbox.

[dunbarx]

And just to beat a dead horse, I actually viewed both the common name and the LC property name for that non-property. One is: "basicTableObject" and the other is "Basic Table Object".

This made me think it had to be a real LC property, and not just not a property at all.

Craig