ed for
> you.
>
>
>
>
>
> *From:* Christopher Karper [mailto:[EMAIL PROTECTED]
> *Sent:* Tuesday, May 06, 2008 11:41
> *To:* Rob Mensching
> *Cc:* wix-users@lists.sourceforge.net
> *Subject:* Re: [WiX-users] SQL Script question
>
>
>
> Fair enough. I know that SQL use
not very enticing to shove the SQL
Script into a record and have it formatted for you.
From: Christopher Karper [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 06, 2008 11:41
To: Rob Mensching
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] SQL Script question
Fair enough. I know tha
u'd need to do
> "[\[]Database[\]].[\[]dbo[\]].[\[]TableName[\]]" to not have them get
> resolved. Which is worse?
>
>
>
> *From:* [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] *On Behalf Of *Christopher Karper
> *Sent:* Tuesday, May 06, 2008 10:42
> *To:* w
t resolved.
Which is worse?
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 SQ
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 difficul
5 matches
Mail list logo
