Not sure if you would want to
Generally with activex/ocx we release them as separate objects, therefore if we want to make a change in one of the controls, we don't have to release the entire exe etc to allow user upgrades.
Good thinking kedaman, but............
.....the problem then becomes the size of the exe, and the additional usage of memory.
Lior
If there is no change to an ocx and it has already been distributed then no you don't have to include it.
Depending on how you load your ocxs etc
It is possible, by excluding ocx controls from exe, to not actually load them into memory until they are used. For example, a utility to format data to excel/word, if it is never actually used it does not necessarily end up in memory.
Hmmm...currently working on something we call Framework
Basically, if ya don't need a feature on your local PC it can be passed off to a server, which will run it when system usage is down. Still having problems with net traffic, so am still trying to figure out the rules for it:(
Had to do it cause a client tried loading a 3 gig database into a spreadsheet....it wasn't pretty:(