Software Deployment

Okey... I will try to add the registry key's.
I get back if I manage it to work or not :)

Regarding the batch file. The application writes down an .cmd file to the program files\app directory and everytime you launch the application it will go through this .cmd file and look at all parameters. Two of the parameters in this file will be different for different departments in the company.

So my thought was to luanch a .bat file that look's if this two parameters are set or not the first time you install the program.
And show me a command promt that tells me to put in the value for this two parameters.
By doing this we at the IT department can put in the right parameters for that specific user/computer when the application installs

Anyone how has a better solution? Probably??

I have found the Windows Installer engine's handling of ODBC via the tables to be somewhat hit and miss. Now, I never use them. Instead, I export the registry data that the application/set-up stub has written and import it directly. Of course, you can edit the Registry table directly, too.

Why would you want to run a batch file? There's very little you can do in batch that couldn't be done via the MSI and with the concomitant advantages of WI like repair, rollback, etc.