Hi

For me, the most known error with dnn, which I meet again & again, is this thing with the sysobjects table in the DB. Everytime there is a new upgrade to a module I get this somehow again...
So, maybe it's time 1 and 4 all - to call all developers to make it a developing rule:

DO NOT USE THIS IN YOUR SQL:
{databaseOwner}sysobjects

Hi

This I know...

But if you change the DBO value in your web.config then {databaseOwner} will become the user you changed to.

When, always, the sysobjects table belogns to 'DBO'.

In the sql file, it seems all ok, you even wrote dbo.sysobjects most of the times, but 1 time is saying: {databaseOwner}.sysobjects - and thats when it falls.

When writing a sql script about this table, you should always use 'dbo.' - that will work for everybody. When using {databaseOwner} it will work for only those who are using the DB as DBO, and didn't change the web.config.

After changing it to DBO.sysobjects - it installed with no errors.

Only now, I have a different error, mentioned in another topic here.

Zip File: Survey_04.00.20_Source.zip

File: 03.03.00.SqlDataProvider.sql

Line 47:

if exists (select * from {databaseOwner}sysobjects where id = object_id(N'{databaseOwner}[{objectQualifier}GetSurvey]') and OBJECTPROPERTY(id, N'IsProcedure') = 1)

Should Be: