One option would be to dump the OCX and call the common dialogs directly via the Windows API. Then I could at least distribute just my zipped VB program and have a corresponding link to the VB6 runtime installer. That way, I'd be able to still have a small, ubloated download for everyone, and only the people who don't have the VB6 and OLE runtimes would need the extra install. This is attractive and I will be investigating it more closely.

This shows you how to do 32-bit common dialogs without DLLs or OCXs (vbAccelerator is an excellent site).

As to VB6 needing all those OLE DLLs, it doesn't really have much choice seeing as the whole of VB6 is based on COM (one of the many alternative names for one incarnation of OLE). It is painful though to write a simple app that compiles to a couple of tens of kilobytes, only to have it bloat to several meg when you distribute it.

At least you aren't struggling with VB4...
(the less said about VB4 the better)

That tool from BitArts looks interesting, but I think I would want to do some testing before relying on it!

Thanks Tony for all your hard work, I never did get the time to complete my logo editor/uploader.

__
Unit serial number 47 (was 330 in the queue)...