08:59:52 AM
3HI0JAF0M
should move up the roadmap ...
I am not sure if this is related but I am looking to eliminate PUBLIC variables in my app and I thought _SCREEN was a valid place to put this data. Should I being doing something else? I am looking to store an oUser object, oData, ...
"Make sure you do not store user-dependent data in PUBLIC variables.
User-dependent data should be stored in form, form members, in _SCREEN properties."
So far, FAS does not save _screen properties
This needs be implemented in a future version
When restoring properties, like in a form refresh, FiC cannot tell the difference between:
_screen.osession.gdCMonDate1 and _screen.osession.gdCMonDate2 .
I instantiate two text boxes, each with one of the two above vars as a control source. In the click of a button I compare the values. If they are not valid, I display a message telling the user to re-enter. That is all. After that point, the refresh cannot tell the difference between those two and BOTH textboxes will display the same value.
-- thn (FoxInCloud)