Using DNN 3.1.0 The following error appears at install.  I stll get the successful Installation msg but the module just doesn't sem to act right.

SQL Execution resulted in following Exceptions: System.Data.SqlClient.SqlException: Line 4: Incorrect syntax near 'trg_ProfileGeoLookup'. at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText) at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions) --** DROP THE PROFILE GEOLOOKUP TRIGGER if exists (select * from dbo.sysobjects where id = object_id(N'dbo.SHAPEHDC_[trg_ProfileGeoLookup]') and OBJECTPROPERTY(id, N'IsTrigger') = 1) drop trigger dbo.SHAPEHDC_[trg_ProfileGeoLookup] System.Data.SqlClient.SqlException: Line 4: Incorrect syntax near 'trg_GeoLookupProfile'. at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText) at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions) --** DROP THE GEOLOOKUP TRIGGER if exists (select * from dbo.sysobjects where id = object_id(N'dbo.SHAPEHDC_[trg_GeoLookupProfile]') and OBJECTPROPERTY(id, N'IsTrigger') = 1) drop trigger dbo.SHAPEHDC_[trg_GeoLookupProfile] System.Data.SqlClient.SqlException: There is already an object named 'SHAPEHDC_trg_ProfileGeoLookup' in the database. at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText) at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions) --* CREATE PROFILE TRIGGER FOR GEOLOOKUP CREATE TRIGGER dbo.SHAPEHDC_trg_ProfileGeoLookup ON [dbo].[aspnet_Profile] AFTER INSERT, UPDATE AS Update X set X.GeoLookup=dbo.SHAPEHDC_fn_ProfileGeoLookup(u.UserId) from inserted u join [dbo].[aspnet_Profile] X on X.UserId = u.UserId System.Data.SqlClient.SqlException: Invalid object name 'dbo.GeoLookup'. at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) t Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText) at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions) --* ADD THE TRIGGER FOR THE GEOLOOKUP TABLE CREATE TRIGGER dbo.SHAPEHDC_trg_GeoLookupProfile ON [dbo].[GeoLookup] AFTER INSERT, UPDATE, DELETE AS Update X set X.GeoLookup=dbo.SHAPEHDC_fn_ProfileGeoLookup(X.UserId) FROM [dbo].[aspnet_Profile] X

A few late additions have been added to the GoMap module, as well as a correction to the install script :

1. The install script failed to succeed when the target database used object qualifiers - this problem had been addressed and corrected.

2. A Positional Timeout has been added which allows you to control in milliseconds a timeout to wait before loading the initial overlay points. This eases a problem experienced by IE users - allowing IE a bit more time to complete its rendering before adding to the html content.

3. An Auto Playback option had been added, allowing you to set the map to not only animate the points on execution of the play button, but to also initiate this automatically on page load.

Any more ideas or suggestions for the map module are awaiting your reviews - let us know what you think, or any questions about the module itself. We Love you feedback!