I have the following situation which is proving to be quite an annoyance. I would appreciate comments:
I have several workbooks (from 300 to 1000K) making up a porgram. The main one loads, the others only upon
demand since it takes from 1 to 2 minutes to load per module. The number of calls between modules is not great,
nor are any called often. To avoid confusion and to allow this loading on demand, all external calls are placed
through the main module via the Run statement. Specifically, a call from Module A to Module B involves two Run
statements, the first from A to the Main Module, the second from the Main Module to module B.
After implementing the above with the Run command, I find that it works quite satisfactorally on the Mac. When
I move it to Win 3.1, however, I wind up with an out of stack space. Now, the conjecture is that in Win 3.1 the
arguments (strings and numbers) are getting pushed onto the stack by value, and the stack size is not large enough.
In addition, however, examining the procedure calls leading to this reveals that where there is a cross module call
in Win 3.1, "non Basic code" is shown as a called routine. The Mac does not have this.
Does anyone have comments or workarounds? A simple solution such as creating a type for the arguments and then
passing only that type is, of course, ineffectual, since the entire type is pushed onto the stack. Moving to
another Windows platform is not an option.