I have a VB app that was originally written for use with SQL 2000 and DMO. Because 2005 only supports SMO natively I have to install SQL Server 2005 Backward Compatibility Components along side the client application to allow DMO to be used on the 2005 DB. This works fine until an update is run on the client application.
After each client update via Install Shield I have to repair the BC components to reinitialize with the new version of my application. Does anyone know of a way to modify the registry after an update, or to do a silent repair of the BC components that will work consistantly from computer to computer? Manually running the repair every time is tedious at best.
Thanks for any response!
After each client update via Install Shield I have to repair the BC components to reinitialize with the new version of my application. Does anyone know of a way to modify the registry after an update, or to do a silent repair of the BC components that will work consistantly from computer to computer? Manually running the repair every time is tedious at best.
Thanks for any response!
