Page 1 of 1
Suppressing PROGRESSTEXT output
Posted: Thu Jan 11, 2007 1:25 pm
by epohl
Another question that likely has a simple answer, but I haven't been able to locate it.
Is there a way to suppress the progress text that appears when running the SQL Server plugin? I'm seeing the exact text of the sql command in that progress text. It's not that I'm trying to be secretive about what I'm doing, but to my eye it looks unprofessional. I tried adding a "Set Variable PROGRESSTEXT" statement right before executing the sql script, but it was overwritten as soon as the sql server statement ran.
Thanks,
Eric
Posted: Thu Jan 11, 2007 2:53 pm
by jimo
What you can do is place an additional text field on the dialog and hide it, then set that text field's caption property to, for example, $VAR1$.
Set Variable VAR1 to FALSE Do this before showing the progress dialog.
Before the SQL Server Install comnand in MSIcode flip VAR1 to TRUE
Back in the Dialog Editor use Dialog Rules to make the progresstext control visible or not.
That should work, give it a try.
Posted: Mon Sep 28, 2009 2:50 pm
by KennethLee
Hi,
I have exactly the same problem and I've tried exactly as jimo said, but it does not hide the progress text.
As a precaution (to ensure I did everything correctly), this is what I did:
1. Created a text field called Edit1 with text, $SUPPRESSPROGRESSTEXT$
2. Created two rules that say if Edit1.Caption is TRUE, make StaticText1 (the progress text) visibility to False. If not TRUE, make visibility True.
3. In MSICode, added statement Set Variable SUPPRESSPROGRESSTEXT to blank.
4. Just before the SQL Server Install command, I did Set Variable ... to TRUE.
5. Just after the SQL Server Install command, I did, Set Variable ... to blank.
Doesn't work. Is there any other method?
Thanks in advanced,
Kenneth
Posted: Mon Sep 28, 2009 3:37 pm
by epohl
I ended up writing a command-line application to handle all of the database calls, and calling the app from the installer. I found for my purposes I did not have enough control using the existing plugins. In particular, I needed verbose logging for troubleshooting problems setting up the database.
Good luck,
Eric