Much of what you have both told me is what I suspected. This also leads me to believe that the problems I have been having with upgrades are due to an "anomaly" in DNN ver 3.3.5. DNN is issueing SQL statements specifying "username.sysobjects", (see the error referenced my
the original post) but apparantly the owner of the table "sysobjects" should always be "dbo"and not "username". This works just fine if they BOTH happen to be "dbo" but my ISP assigns the username as the owner to non-system created files. This has not been a problem with versions through DNN 3.2.2 - since the system tables were not referenced by the username.
I don't want to go through process of changing ownership, since I will have the same problem next time upgrade and it may cause problems everytime I add a new module, since the ownerhip is automaticly going to be the username. I'm not even sure it will solve the immediate problem. Also I do not think the script that john posted deals with the stored procedures.
For the time being, i would like to change the particular reference that is causing the problem, but I do not know where it lives. I also think it should be submitted as a bug.
So, anyone know how to find the references to "sysobjects" and change them so that the username is not prepended as the database owner?