> But I found a new problem. Now that I single threaded it, the timelock
> dialog shows up BELOW the New/Open dialog. In dual threads, the timelock
one
> came up on top. How do I fix that? The time lock is coming up in the open
> application message.
As a guess...which it is...your timelock code required that the one thread
relinquish control until the timelock thread had finished its work and said
it was okay to continue. Now with one thread, both are executing in an
order, which is different from what you intended it to do. As a suggestion,
your code should check first, in the MSG_GEN_PROCESS_OPEN_APPLICATION whether
it is okay to continue by running the code and thereby abort if it's not...or
to continue.
You'll have to figure out another way to implement your timelock code, or not
use it while you are developing your application, until you are ready to
release the finished product.
Lee