New version of VB Lite Unit

In case no one has checked in the last few days, I put up a new revision of VB Lite Unit (1.2.3) on Sourceforge - http://sourceforge.net/projects/vb-lite-unit.

This revision has a lot of the fixes and features y'all have been asking for including a progress indicator.

I've recently learned some things the hard way about working with these DLLs that you might want to be aware of.
1. It's possible to have 2 copies of the same library registered, and this -will- cause problems when you try to use it.
2. It doesn't work to try to unregister a DLL after it has been deleted or replaced with a different version. Instead, you have to spend a 1/2 hour deleting all traces of it from the registry.
3. When you build an ActiveX DLL in Visual Basic, it is automatically registered in the path in which you built it - along with any version previously registered.

So, this leads me to recommond the following practices:
1. Before replacing a registered ActiveX DLL or building a new copy in VB, unregister the old one. Do this using regsvr32.exe /u <full-path>.
2. After building an ActiveX DLL in VB, and before moving it to a permanent location on a hard drive, unregister it in its build location, then re-register it in its permanent location after moving it.