The one form, one program approach

Many people wrote programs where you had one program to handle each form in the system. Although this works fine for older Superbase programs, it becomes a nightmare for larger ones. This is because:

You wind up duplicating information in many of the programs.

You have as many program files as you have forms. In a large form system this can be a lot.

Each movement to another form requires that you handle switching to a new program file.

Each movement to another form requires that you account for global variables and the requirement to "jump down" into the program somewhere.

In Superbase 2.xx and beyond, this approach no longer makes sense since you can have reusable procedures, and code libraries that lay resident in in memory.