>In the work I've done to date, I've created some classes that I've used for a few apps. Since these classes were relatively small, I just compiled them with the EXE. Now, I'm going to distribute the Stonefield Class Libraries with my app. These classes are fairly large and make a significant difference in the size of the EXE. It seems to work just fine if I exclued the classes from the complied EXE and just make sure they are in the app directory. Are there any pros and cons to (1) Including the class libraries in the compiled EXE or (2) Not compiling them in the EXE and just including them in the distribution set-up?

To clarify one point, you can remove the SP source code from the DBC but it is different than removing the code from a VCX/SCX. You still open the DBC as a table. The source code is in the CODE field of record 3 or the record whose ObjectName is StoredProceduresSource. The compiled code is in the CODE field of record 4 or the record whose ObjectName is StoredProceduresObject.

When you compile everything into the app, the resulting size of the APP/EXE depends on whether or not you have the DEBUG option checked under the Project Options. If unchecked, the source code is not included in the APP/EXE. You get a smaller APP/EXE but you lose some debugging information that is usually passed to error trapping routines.