I would suggest you first edit your web.config file to set CustomErrors mode to "Off" then load the modified web.config back up to the host server.  When you hit the site again, you should be able to see a more detailed error message which you can post here if you need further help.

Your post's subject line "Wrong Database . . . " indicates that you may have some additional information leading you to that conclusion. Could it be that you forgot to set the ObjectQualifier value in the new web.config to that used previously in the 3.2.2 install? This will really mess up the database and result in a server error.

Bill, I changed shut the custom error off and this is what it showed after hitting the site again. Let me know that you think. Thanks!Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Could not load type DotNetNuke.UI.WebControls.CaptchaHandler from assembly DotNetNuke.

Source Error:

Line 57: 			<add verb="GET" path="FtbWebResource.axd" type="FreeTextBoxControls.AssemblyResourceHandler, FreeTextBox" />
Line 58: 			<!-- This is for CAPTCHA support -->
Line 59: 			<add verb="*" path="*.captcha.aspx" type="DotNetNuke.UI.WebControls.CaptchaHandler, DotNetNuke" />
Line 60: 			<!-- This is for Serving files, secure, insecure, from database -->
Line 61: 			<add verb="*" path="LinkClick.aspx" type="DotNetNuke.Services.FileSystem.FileServerHandler, DotNetNuke"/>

Server Error in '/' Application.

---

Configuration Error