Re: [WiX-users] ODBCDataSource formatted strings for dynamic naming

2010-02-26 Thread Bob Arnson
On 2/24/2010 11:37 AM, Jake Boone wrote: > When is the best time to schedule the update to the table? > Before the InstallODBC and RemoveODBC standard actions. > Looking through the available functions, it looks like rows can only > be inserted or deleted, not updated. Is that correct? >

Re: [WiX-users] ODBCDataSource formatted strings for dynamic naming

2010-02-24 Thread Jake Boone
Great, thanks for the response. My registry search is done in a C# custom action before LaunchConditions. When is the best time to schedule the update to the table? Looking through the available functions, it looks like rows can only be inserted or deleted, not updated. Is that correct? Can an

Re: [WiX-users] ODBCDataSource formatted strings for dynamic naming

2010-02-24 Thread Bob Arnson
On 2/22/2010 3:38 PM, Jake Boone wrote: > The only problem seems to be that ODBCDataSource/@DriverName and the > nested Property/@Value are not formatted strings. That's how the MSI ODBCDataSource table is set up, so WiX can't change that behavior. You could write a custom action that updates the

[WiX-users] ODBCDataSource formatted strings for dynamic naming

2010-02-22 Thread Jake Boone
I am creating a System DSN in my installer using an Oracle ODBC driver. I am resolving the name and version of the driver with a custom action (I have to loop through the Oracle registry hive, otherwise I would have used RegistrySearch) during the InstallUISequence before LaunchConditions. The on