>Thanks Hilmar,
>
>We just had a program abort in a certain situation. Both prgs compiled to well over the 64K limit.
>
>The user went into Prg One, the form displayed, clicked cancel then selected the Prg Two from menu. Prg two aborted. Tracing (via the debugger)we found Prg Two's form never Inited, control transferred to a unique function in Prg One. This had myself and a colleague stumpted until that 64K limit memory came back.
>
>We've since pared down one Prg and split the other. Initial testing looks good - no aborts.
>
>Neither my colleague or myself had ever seen this behavior. Funny thing, both these prgs have compiled to over 64K for sometime according to the system administrator without any problems.
>
>
>Again thanks.

Interesting.

I never had this problem - it seems my procedures are smaller.

And I never knew what would happen when the limit is exceeded.

Perhaps the end of the program (beyond 64 KB) wasn't reached for some time?

Hilmar.