>The name doesn't need to be unique but the data in the file needs to be unique and needs to be set prior to running the installation. For example, I may need to set a flag as to whether the system purchased is single or multi user. Or, maybe a record that tells how many customers they are allowed to add based upon which version they purchased...

Paul,

I do something similar. I have a generic installation and when the user installs, they basically have a demo system. In order to activate a real system, they need to have an encrypted keycode that I generate. When they enter the keycode, I have a program that will read it and set all the unique attributes (#users, optional features, etc.) for their installation to the registry. This has worked well for me since users can purchase additional licenses or optional modules and all I need to do is give them a new keycode. No additional installation required.

Kind Regards,

Mat