Yeah. <smile/> WcaGetPropertyString, looks up the Property name passed in and
gets a value. You can't pass in "Please, resolve this [Property] for me" and
get back "Please, resolve this PropertyValue for me". You'd have to process
the SQL Script looking for [Property] strings and update them.
To further complicate matters, SQL uses square brackets to delimit names
itself. This is common [Database].[dbo].[TableName]. None of those are
property names so you'd need to do
"[\[]Database[\]].[\[]dbo[\]].[\[]TableName[\]]" to not have them get resolved.
Which is worse? <smile/>
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher
Karper
Sent: Tuesday, May 06, 2008 10:42
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] SQL Script question
Why is it that SQLScripts don't use property replacement, but SQLStrings do?
It's a real hassle to break large DB deployment into dozens of smaller SQL
string elements, when the sql script action should be able to do everything I
need.
Am I missing some technical limitation that makes it difficult to run the
statements through WcaGetPropertyString before adding them to the statement
buffer?
Chris
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
