all,
as the tilte says;
would it be possible to create a new MSI table only as a means for passing parameters to a deferred custom action?
I need to install 4 databases,
but the built in SQL components are too limited..
I want to give my users the opportunity do define data and log file locations, grow parameters.
so I have a script that can do this, but it takes about 13 parameters per database...
i know i can pass an array of parameters to a deferred action osing the set_parameter custom action. but this approacht is still very inconvienient.
so I was thinking to create a new table with 13 colums, one for eacht property.
and populate it with the necessary data. this will result in 4 records in the table..
then i need to find a way to iterate this table in my custom action and create a database for eacht record.
is this a good idea? or will it not work.
does this break any ICE checks?
many thansk for yor feedback!
regards
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Creating a new MSI table to pass parameters to def
Started by
MrSensitive
, Mar 21 2007 09:56
3 replies to this topic
Posted 21 March 2007 - 10:31
never mind...
I just found out that the database cannot be accessed in deferred execution..
I just found out that the database cannot be accessed in deferred execution..
Posted 21 March 2007 - 18:47
CustomActionData is the only way, or an external file.
Stefan Krüger
InstallSite.org twitter facebook
Posted 22 March 2007 - 10:54
ah, an external file, that might be a solution..
altough i was already implementing it using CustomActionData
which, as it seems, is not so difficult as first thought..
many thanks.
altough i was already implementing it using CustomActionData
which, as it seems, is not so difficult as first thought..
many thanks.