Hi Craig,

That's not a problem. I've got a good updating procedure that replaces the exe wherein the controls are built.
As I see it, when a user does an update, I have to:

- copy the new controls into the main app folder (or one of its sub's)

then, when a user logs in from an installed workstation,

- identify the controls' location (they're all in the same place), likely using the registry, or just a robust if file()...
- determine whether the controls need updating...
- if so, un-register the old ones...
- check if it's successful...
- delete the old ones...
- copy the new ones to the same location...
- register the new ones...
- check if that's successful...

So I think what I need to know is how to get the registry to cough up where they are, and how to capture the return value of the regsvr32.exe call, if that's what I should use.

No problemo, right?

Luke