Posted 18 July 2007 - 21:10
What I did, and I regret, was built a custom dialog to get the password in the event the user already had MSDE 2000 installed and had a password.
I took the value and stored it, and then passed that into a batch file using %1, which installed MSDE 2000.
The problem is, when you try to repair the program, it fails and you have to manually enter the password in the batch file and run it separately.
I don't have a better solution as we've moved on to SQL Server 2005, but I thought I'd throw that out there as to how not to do it ;P