Once more thing, I missed this before because you said that you had replace 'dbo' in your project with 'EXP0'.  But just double-check your web.config's data provider.  In the data provider section, the database owner is specified:

<data defaultProvider="SqlDataProvider">
     <providers>
          <clear />
          <add name="SqlDataProvider" 
               type="DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider" 
               connectionStringName="SiteSqlServer" 
               upgradeConnectionString="" 
               providerPath="~\Providers\DataProviders\SqlDataProvider\" 
               objectQualifier="" 
               databaseOwner="dbo"/>
     </providers>
</data>

Ahh...  DH hosting... That is a whole new situation.  :)

It sounds like the DNN installation was done using DBO as the schema.  Following your project migration, this changed (obviously).  If you are installing DNN locally and then moving it later, you would be better off creating and using the "EXP0" schema in your local DB instance to prevent these migration headaches when you deploy your project. 

I would also suggest that you consult with your DB host first to ask what their schema naming structure is to be sure that you can safely assume what the schema will be upon migration of the data.  If it will always be a similar naming convention, then emulate that locally to help you deploy easier.

Once you find all of the references to DBO, it will indeed work.  Nearly all of your SPs have references to the DBO schema.  The DNN framework uses the GetDataBaseOwner method for all of the code references to schema.  This method pulls directly from the web.config section that you verified.  So, I am guessing that once you get the database views and stored procedures updated with the correct schema references, all should work fine.