>>The ProgID and VersionIndependent ProgID remain the same. My CLSID for VisualFoxPro.Runtime.6 now reads {008B6021-1F3D-11D1-B0C8-00A0C9055D74}; I'd assume that MS follows its own rules, but they've been known not to do that in the past...any time I change a registered component, I re-register, since it can't hurt.
>
>Well, that's what I *thought* (and hoped), but I've been known to just drags bits for certain products and have it work because the CLSID never changed. Couldn't remember if that was the case with VFP or not.

The SP4 registered a change to a registry key value during its install process (yeah, I make sure to track things so I know what happened when they fall down go boom...) The distributed MDAC_TYP.EXE puked on me and said I already had the latest version (probably from a download last week) and refused to run on my 2K Pro box before I applied SP4, and it also updated some controls for things other than VFP that may be of interest, so I'd guess that redistribution of any runtimes from SP4 ought to include reregistration, and a little care to ensure that you don't need to use delayed copy and registration (IOW use an installer to put it in place rather than doing blind copies, especially under Win2K.)