ActiveX controls, especially, but not limited to, "home grown" ones, are notorious for being hinky! And as you said, you do have to register it on ever machine that will be running it! This could make it particularly troublesome for a distributed application, where the developer might have little or no control after distribution. You deliver the app to a client, go on with your life, and two years later they decide to upgrade their computers and "Bam!" your app doesn't work anymore! Could take someone a really long time to figure out what went wrong with a custom ActiveX. And then, of course, there's the question of new versions of Access. The only version I saw mentioned at paperwalker was Access 97. Stephan has always kept his up to date with the latest version of Access. That'll no longer be necessary, of course, since after all these years, Micro$oft finally saw fit to address the problem themselves! Version 2007 has a built in function to handle all this.
Bottom line is I wouldn't be afraid to try it out on an in-house project that's never going out of my hands, but would be very leery of distributing it. I'd also be sure to make notes at the top of the code module on my main form, reminding that the control needs to be registered if machines are replaced.
The Missinglinq
Richmond, Virginia
There's ALWAYS more than one way to skin a cat!