Like I said, there is a bug in the webappbuilder that doesn't change the Server.CreateObject in the new web site's default.asp because the webappbuilder is looking for the wrong thing. It is looking to change avfpdemo3, but the sample default.asp contains AVPFdemo3 (note lower case vs upper case). To fix it, you can either change webappbuilder or the sample default.asp in the avfpdemo3 website.

The data type mismatch error you get when generating a new web site is due to another bug in the webappbuilder. If you don't use dotnet, then there is a variable that winds up being a boolean instead of a string (null or otherwise), which causes the data type mismatch when webappbuilder runs.

June

>>Check to see if there is a 'hello' case statement higher up in main.prg. It probably is looking at that first.
>
>
>The usual cause of this event is the newly created website is looking into the DotComSolutions virtual website in your IIS wwwroot for its result, instead of the new ActiveVFP virtual webs that Postsetup creates. So, when the change is made to the 'Hello World' VFP event, the new web site still finds the DotComSolutions ActiveVFP which refers to the DotComSolutions folder.
>
>I still get errors when I generate a new site and when I run PostSetup as well. But, I noodle my way around the errors to get things running.