Try
If REMOVE="ALL" Then....

(There must be double quotes around the "ALL")

...The addition of '~' avoids the need for the user to specify "ALL" in all upper-case. The 'REMOVE' part must always be in all upper-case, obviously.

I have entered it as REMOVE~="All", but still not working. Anyways, it does seem to "go into" the if statement because in the log I can see that it sets the property etcetera. Also, in the log I can see an error message saying that it cannot establish the SQL connection.

Anyone any idea about why the SQL connection cannot be established in the uninstall? Do I need to specify somewhere that on REMOVE the connection must be configured? If so, where? 

Thanks,
Katrien

...the connection to the d/b needs to be defined, unless you have somehow conferred psychic powers on your package. I figure one of the creation scripts has to contain the connection details. Use those.

When I add the sql scripts in WISE I use the sql connection properties as defined in the gui window there. In the MSI script I can see this translates to a statement like this:

Set Property WiseSqlCallID2 .... DRIVER={Sql Server};SERVER=(local); ...

(see also my very first post).

I import the uninstall script in the same way as I import the install script. The only difference is that in the MSI script editor I make some changes in the execute immediate and execute deferred. Please see my first post. So, I don't have psychic powers ...

...you've run the uninstall SQL script outside of the MSI and proved that it does the job?

I've done that indeed. And it works.

So perhaps I can rephrase my question.

I have a sql script that runs fine, I added it using the "SQL scripts" GUI in WISE. I would like this script to run on 'remove', not on 'install'. So what I've done is edit the condition to set the property and call the script in respectively Execute Immediate and Execute Deferred. I edited the condition from:

(!Complete = 2 AND &Complete > 2)

To

(REMOVE~="ALL")

But it doesn't work.

Can someome let me know if they've managed to run a sql script on the uninstall or remove events? And if so, how did you do this.

Thanks,
Katrien

If the connection requires authentication you'll need to pass that.
If you run the custom action in deferred execution then you would need to make sure the local system account has the correct credentials to make a valid connection.

Ok, I understand that. But that has nothing to do with my problem - in my opinion.

It works fine when I use the constraint: (!Complete = 2 AND &Complete > 2)

It does not work when I use the constraint: (REMOVE~="ALL")

That's what is the problem. So I need to configure something on the remove event that is configured on the install event. But what? 

Anyone an idea? 

Looking back over the thread, there are references to the uninstall custom action being placed in the immediate and the deferred sequences,  but there is no actual information on where in these sequences your CA is actually placed.
Since the REMOVE property is not set to "ALL" until the InstallValidate action, any CA sequenced before InstallValidate which tests the REMOVE property is not going to work correctly.
Examining a verbose log of the uninstall will give you information about the values assigned to properties, etc.

I am really disappointed about not getting this to work. In InstallShield you can simply add a SQL Script and select "run on uninstall". You would think that this is something that is used often in database installations.

I am only using WISE in trial mode, but don't think I will buy the full version. It's too fiddly to get it to work.

... that when selecting that option, all IS does is add the REMOVE~"ALL" condition to the CA. It just does it "behind the scenes".

IS has its own challenges, like its brain-dead presentation of Custom Actions (amongst other UI foibles). I also find its MSI compilation glacial, to say the least.

Well, at least it works in IS! And adding the condition to the CA doesn't work for me in WISE.