I'd love to share it - that was the whole intent of this excerise from day one !

I decided to write it in C++ because I wanted a library (DLL) that could be easily "inserted" (copied) into the KiX distribution package and wouldn't need a bazillion megs of VB runtime library support.

I wrote kixtart.library with MFC support and statically linked it with the DLL. Even though the library supports a handfull of functions (api calls) the full-blown version DLL size is 139,264 bytes (not bad) and no other dependencies. With dynamically linked MFC, the DLL would be invisible ( ok, maybe not invisible but real small).

Adding functions to the library will only consume incremental space from now on !

Don't know how you feel about C++ but I reckon that developing a KiX support library in Visual Basic will generate a lot of push-back from the KiX community.

I'd be more than happy to send it to you or discuss this further if you really want to roll-your-own with VB !

Shawn.