Hello, all--

I have an unstored calculation field called c_allOpenWindowNames on LayoutA:

WindowNames("myDatabase.fp7")

Obviously, it shows the names of all open windows.

But if a user navigates to one of those open windows before clicking on one of several buttons in LayoutA, he/she will change the window order and that change will not be reflected in c_allOpenWindowNames, yielding an unexpected result when the button is clicked.

So my question is: Is it possible to force the unstored calc to refresh the moment the user switches back to LayoutA --so it accurately reflects the newly changed window stacking order? Hope that makes sense. Many thanks--

Don't store the data in a clac field, call the function directly in the script or whatever.

Thanks for your reply, Vaughan--

A few more details:

There are five buttons on the layout. The user will choose/click a button based on what he sees in the c_allOpenWindowNames field. That's why it's critical that this field accurately reflects the current window stacking order before any script is called.

Realizing the limitations of an unstored calc field, I'm not sure this is going to work.

The limitation belongs to screen refreshing (lack thereof), not to the calculation.