Kevin:

I am getting EXACTLY the same error after updating MM.NET from 1.1 to 1.2. As long as we know what the fix is, I guess it is ok albeit annoying.

I am getting an apparently security related error, though, which I haven't been able to track down, yet (not enough hours in a day to debug an app that used to work fine until framework version update happened...)

Since you know your framework inside and out, could you give me some ideas as to where this error might be coming from? I would really appreciate it.


Prepared statement '(@UserFK nvarchar(4000)) SET FMTONLY OFF; SET NO_BROWSETABLE ON;' expects parameter @UserFK, which was not supplied.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: Prepared statement '(@UserFK nvarchar(4000)) SET FMTONLY OFF; SET NO_BROWSETABLE ON;' expects parameter @UserFK, which was not supplied.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding he origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[SqlException: Prepared statement '(@UserFK nvarchar(4000)) SET FMTONLY OFF; SET NO_BROWSETABLE ON;' expects parameter @UserFK, which was not supplied.]
System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
System.Data.SqlClient.SqlCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
System.Data.Common.DbDataAdapter.FillFromCommand(Object data, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable)
OakLeaf.MM.Main.Data.mmDataAccessSql.FillDataSet(DataSet ds, IDbDataAdapter dbAdapter, String tableName, Boolean clearOnFill)
OakLeaf.MM.Main.Data.mmDataAccessSql.FillDataSet(DataSet ds, IDbCommand command, String tableName, Boolean clearOnFill)
OakLeaf.MM.Main.Data.mmDataAccessSql.FillDataSet(DataSet ds, String command, String tableName, CommandType cmdType, IDbDataParameter[] dataParms, Boolean clearOnFill)
OakLeaf.MM.Main.Business.mmBusinessObject.FillDataSet(DataSet ds, String command, String tableName, String databaseKey, CommandType cmdType, IDbDataParameter[] dataParams)
OakLeaf.MM.Main.Business.mmBusinessObject.GetDataSet(String command, String tableName, String databaseKey, CommandType cmdType, IDbDataParameter[] dataParams)
OakLeaf.MM.Main.Business.mmBusinessObject.GetDataSet(String command, String tableName, String databaseKey, IDbDataParameter[] dataParams)
OakLeaf.MM.Main.Business.mmBusinessObject.GetDataSet(String command, String tableName, IDbDataParameter[] dataParams)
OakLeaf.MM.Main.Business.mmBusinessObject.GetDataSet(String command, IDbDataParameter[] dataParams)
OakLeaf.MM.Main.Security.mmUserSecurity.GetUserSecurityByPK(Object userPK)
OakLeaf.MM.Main.Security.mmSecurityManager.GetAccessLevel(Object userPK, Guid securityID)
OakLeaf.MM.Main.Web.UI.mmUIHelper.RegisterSecurity(Control control)
OakLeaf.MM.Main.Web.UI.WebControls.mmDataGrid.RegisterSecurity()
OakLeaf.MM.Main.Web.UI.WebControls.mmDataGrid.OnPreRender(EventArgs e)
System.Web.UI.Control.PreRenderRecursiveInternal()
System.Web.UI.Control.PreRenderRecursiveInternal()
System.Web.UI.Control.PreRenderRecursiveInternal()
System.Web.UI.Page.ProcessRequestMain() +1489


>Chris,
>
>>And I was able to open the file normally, no errors like before. Then I changed the definition of the class back to the way it was originally, without the explicit reference:
>>
>>

>>public class ABusinessObject : mmBusinessObject
>>

>>
>>And it worked when I tried to open it again normally. Anyone have any idea what's going on?
>
>I'm not sure why you experienced this in the first place...sounds like a VS .NET issue since you didn't really have to do anything to fix it! I just tried this again myself and couldn't reproduce it on a new, clean machine.
>
>Regards,