Article ID: 35717
Article Last Modified on 11/21/2006
This article was previously published under Q35717
SUMMARY
Under the Apple Finder, the SubLaunch routine will remove the launching program from memory before loading the launched application.
Under Apple MultiFinder, the SubLaunch routine keeps the launching program in memory in addition to the launched application.
Therefore, invoking SubLaunch under MultiFinder can require a lot of memory because both the launched and launching applications will be in memory at the same time. If there is not enough memory to load the SubLaunched application, the launching program will continue at the next statement and the specified application will not be launched.
MORE INFORMATION
SubLaunch is an MBLC library routine in QuickBASIC that transfers control to another specified application. When the launched application terminates, it returns to the launching program.
We recommend that you use the FILES$(1,"APPL") function to select the application to SubLaunch to be sure that the path and file type are correct.
WARNING: SubLaunch does NOT verify that the program exists, or is actually an application. If the name specified is not a type APPL file or does not exist in the specified location, you will get a system bomb. SubLaunch does NOT automatically flush file buffers or close open files. We recommend that you perform a CLOSE or RESET before invoking SubLaunch. You also should make sure any open resource files are closed.
Microsoft also recommends using SubLaunch instead of the Transfer ROM routine because Apple no longer supports the Transfer routine. Transfer may not work correctly under versions of the Macintosh System from Apple later than Version 4.20. Transfer is being replaced by SubLaunch.
Additional query words: MQuickB
Keywords: KB35717
