Hi Mark and Jacqueline, The substacks had PreOpenStack handlers that called a library stack and sometimes emptied out some fields, but what they did not have OpenStack handlers. The absence of OpenStack handlers appears to have been the problem because, after the the sub-stack executes its own PreOpenStack, the main stack, for whatever reason, executes its OpenStack. This, of course, can be disastrous if the main stack is intended to initialize an app or perhaps contains sensitive material that should not be revisited! My fix is to include an OpenStack handler with nothing in it in every sub-stack in order to trap the message.
on OpenStack — Do nothing end OpenStack Gregory _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
