OK, this is a bit of a rant, but relatively important.

Probably 40% of my support requests from DNN hosting customers are regarding third party module installations failing due to either not using {databaseOwner} and {objectQualifier} or using {databaseOwner} on the sysobjects table.

I realize that the Module Developers Guide explains the use of {databaseOwner} and {objectQualifier}, and the example table creation script on page 42 shows the proper use of {databaseOwner}, {objectQualifier}, and dbo.sysobjects, but could a explanation of the sysobjects be added to the guide?

When I run into a module that doesn't use {databaseOwner} and {objectQualifer} I explain these to the customer and CC the module developer with a reference to the Module Developers Guide.  I'd love to be able to do the same with dbo.sysobjects.

Can you believe I actually had a well known commercial module developer tell one of my customers, "This is caused by a wrong SQL server installation. The sysobject is directed to a wrong database owner (dbo)... You must ask your hosting provider to change also the dabase owner for the sysobject. If your hosting provider will not solve this problem you must perform a search and replace operation for {databaseOwner}sysobjects -> sysobjects .", after that customer had paid for thier module!

Talk about frustrating!