Look at design functions. Note that where they say "table", they mean "table occurrence".
Where are you referring to.
Ok figured out what you meant
Some things seem to be there and I may be able to use but didnt see accounts anywhere nor can these functions be part of a value list in FM10A
didnt see accounts anywhere
No, and you won't - because of the potential security risk involved. You can track your accounts in a table, but I'd think twice about that if the data is sensitive.
nor can these functions be part of a value list in FM10A
I am not sure about that. What do you want the value list to show?
lets just take the layout names for instance
How would I get them to appear in a value list
Im headed out Ill look at it this weekend.
I didn't realize this was possible :smileysurprised:
1) You are using a calculation which FM says can't be indexed and it still works as a value list (even when adding new layouts).
Does this only work because it is a design function?I answered this myself with further testing ... no, it works for any unstored calc even Get() functions.
2) The value list is using only related values from Table which (by changing perspective from 'all values') produces all values from a one-record table (unstoredVL) . This means that multilines can be used!
OMG, I can create calc (UNSTORED) in UnstoredVL which is
Let ( [
ts = Get ( CurrentTimeStamp ) ;
s = Seconds ( ts )
List ( s ; s+50 ; s+100 ) ) and it works as value list and the values change every time the field is popped. It also works using calculation (unstored) based upon new child table data as: List ( Child::text ). We are no longer limited in value list use - we can use unstored calculations!!
Incredible. Revolutionary. Thank you so much.
Thank you so much this works great so TableNames is actually occurances though right?