I think I have figured out how not to uninstall the object. In the
Installing() function for my DAO Component I use:
Disable(LOGGING);
and in the Installed() function for my DAO Component I use:
Enable(LOGGING);
I have tested this successfully myself but it has not been tried out by QA
yet. I would be interested in hearing if it works for you. (That is if you
are still working on this issue after all this time).
Thanks,
David Stiff
Trango Software
http://www.trangosoft.com
"Todd Nelson [344434]" <mn_swi...@hotmail.com> wrote in message
news:3ab7...@12.41.20.38...
> The un-registration error on DAO2535.tlb during uninstallation has NOT
been
> fixed.
>
> Setup installation made with Installshield Professional - Standard Edition
> 6.22,
> with the "VB 6 Runtime Object", and the "New DAO 3.5 1" objects added.
>
> Attempting to uninstall the program from Windows 95 results in an
> un-registration error on DAO2535.tlb.
> (a reboot occurs after installation, the program was run to verify it
worked
> (it has no locked or OS files), the OS rebooted, and uninstall attempted
on
> a clean boot.)
>
> Also, when the installation is run more than once on a Windows 95 system,
> the user is forced to reboot each time.
> If the Common control (VB) libraries are updated, and the DAO files are
> updated - Why does the user have to reboot again since all OS files were
> updated already. Obviously Installshield is removing VB and DAO updates
> when it does not have to.
>
> **** This problem is mentioned (and unanswered) in two other emails
here:
> ****
>
> HOW do you set Installshield NOT to uninstall the OS support objects???
> This would fix the problem. Can anyone help?
>
> Thank you,
> Todd
>
>
This does work :).
Tom
"David Stiff" <dav...@trangosoft.com> wrote in message
news:3c14d69e$1...@news.installshield.com...
"Tom Yates" <tom-...@bigfoot.com> wrote in message
news:3c15ee23$1...@news.installshield.com...