Suggested for lar apps:

app_dddw.pbl              // dropsdown datawindows
app_fnc.pbl                  // functions
app_str.pbl                   // structures
app_reports.pbl             // reports
app_license.pbl             // Keep all of your licensing code in a separate PBL, makes it easy to update licenses
app_.pbl

I like to break the code into functional modules after the basics have been covered (dddws, functions, and so on). All of the code that handles user-capable table  maintenance would be in app_table_maint.pbl, for example.

Keeping your code broekn up into logical groupsing really helps make it easy to maintain and update.

Oh, and use the standard naming conventions as well. That way you can look at an object and know into whioch PBL it belongs.


Olan