What is the point in using the SelfReg table instead of the advertising tables provided(Class, ProgId, TypeLib and sometimes Registry)?
For example I downloaded the MSJet 3.5 merge module today and all COM files were in the SelfReg table. Granted that all COM registry keys will get created but if some of them got deleted they would not be repaired correctly. I had to capture the COM information manually and move it to the Registry table and link to the correct MSJet components. In the downloadable DAO 3.51 merge module all registry keys were in the correct tables but both files were still registered via SelfReg table.
Isn't this also against MS Best Practises?
This is not a criticism but just a thought that is there a specific reason for sometimes using the SelfReg table?
And apologies for the typo in the heading...
Edited by Petch, 04 July 2006 - 15:14.