From what I remember (and its been at least 4 yrs) working with SBT, the SBTW.exe is exactly as you read... a simple program entry point to launch the rest of the app. The rest of the app is NOT part of a project that has everything interconnected and joined into a single SBT.app, but calls the sbt.prg (.fxp). The approach they had was to allow you to customize certain portions of the app and recompile only those parts without having to kick everyone out of the system for an update. Just rebuild the screen, re-generate and go.

One of the other things I do remember was this batch file that would copy what appeared to be an entire directory of .prg files into a single SBTPROC.prg, then compile that. This is a central basis for the SBT operations as in the beginning part of SBT.PRG, it does a set proc to SBTPROC -- common functions, string manipulation, user login / access, etc.

Another item I remember was a PITA with some screens having to be rebuilt -- such as Accnts Receiv or Sales Order -- where you have a parent / child / child window schemes - ie: Order header, Order Detail, Order Detail Extras/Notes. If you made a change to one of the children level forms, you actually had to change the primary form, in this example the Order Header as it contained stuff in the snippet areas that the SBT screen generator would use to reference each of the children screens and update accordingly.

I'm glad I'm done with those SBT days, but hope this helps some -- again about 4 years out of SBT.

Don