First let me say, "Great Job Geert"

Now on to my observations so far. Installing using Windows Authentication seems to work like a dream. Bing, bang, boom I had the site up and running.

Installing with a generic SQL user account however seems to have some issues. The user account is added to the SQL database without any problems it isn't getting db ownership rights. I've now given it ownership permissions but is throwing the following error: ERROR: Could not connect to database specified in connectionString for SqlDataProvider. But I can connect to the database with no problems through Query Analyser.

I'll keep testing and will try to see what's screwing up on my local system for sql accounts but thought I'd post whatever observations I had so far. Maybe it isn't just me.

Eureka!!! Okay, this is what I've discovered. You can't mix Windows Authentication and SQL Authentication. In other words, you can't use WA to create the database then assign an SQL user account as the db user.

Also, it appears that when using a SQL account you have to check the "Create SQL Login Id" regardless of whether the account already exists as a user on another database or the proper permissions aren't set on the user account.

I didn't try doing an SQL create database with a Windows User DNN account (trusted connection) so I didn't catch that one. I just noticed that I had to Create the SQL Id even when I was using an existing SQL account and an sa SQL user creating the db.

I think you're on the right track with the safest way to update the user. Is there anywhere we can download the code to take a look at it?