Flow definitions are independent of packaging options, except for client/server applications. When creating the Dialog Flow Diagram (DLG) for a client/server design, you do need to consider which procedures are packaged as clients and which are packaged as servers.
An application runs most efficiently if each load module contains procedure steps that are likely to be used together.
Packaging an entire application into one load module is desirable in some situations. However, it can result in a large load module that may be too large to fit in available memory and therefore cannot be executed.
If you want to package your application into multiple load modules, each must be accessed separately. However, you do not have to completely close one application to invoke another; you can minimize one load module into an icon and access another load module. This keeps both load modules in RAM for faster access, so the only limitation is the availability of memory.
