Friedrich,

One of my clients IT staff is testing the SB install of my latest *upgrade*
to one of my packages.
He reported this to me:

"[after running upgrade installer]... I realised the following files are
missing; Uninst_TCS Store Manager 5.exe & Uninst_TCS Store Manager 5.log.
This means even when I go into Win -> Control Panel -> Add & Remove Program;
it still can not remove the SM program and files at all. I have to delete
all files in the working folder manually, and also the registry."


I have *always* just included the Create Installation Log in my scripts...
with the default installer log name.
As we know, there was a problem with SB until a few sub-versions ago where
the log file was over-written and re-started, but recently it was
over-hauled to append to any existing log of the defined name.

But he is reporting to me that the existing log file is just DELETED (along
with the associated uninstall exe).
I tested his assertion, and he is quite right!!

But the Create Installation Log IS present.. default name.. and overwrite
UN-checked.

I changed the setting to *OPEN* installation log.. re-compiled.. and now it
works as it should, i.e. my upgrade appends to the log

But my understanding - backed up by help - is that it should have done that
anyway.

What is occurring?
What could have the existing LOG and EXE be *deleted* and not even replaced?
Is "Open" the log now the correct protocol?

Steve