Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
MM 3.5 Error after conversion
Message
From
28/05/2008 11:22:57
 
 
To
27/05/2008 18:06:56
Timothy Bryan
Sharpline Consultants
Conroe, Texas, United States
General information
Forum:
ASP.NET
Category:
The Mere Mortals .NET Framework
Miscellaneous
Thread ID:
01319790
Message ID:
01319978
Views:
13
By converted I meant migrated. I may end up having to restore the version 2 business objects and manipulating them manually, but that seems counter productive.

I tried creating a net new project and generating the business objects again and then just moving my code over. The result was the same. First off I selected dynamic SQL and the command type was still set to stored procedure and secondly the error persisted. When I issue a saverow I get the following error stream:

[NullReferenceException: Object reference not set to an instance of an object.]
OakLeaf.MM.Main.Business.mmBusinessRule.CheckRules(mmBindingList`1 entityList) +89
OakLeaf.MM.Main.Business.mmBusinessObjectGeneric`1.CheckRules(mmBusinessObjectGeneric`1 businessObject, mmBindingList`1 entityList) +747
OakLeaf.MM.Main.Business.mmBusinessObjectGeneric`1.CheckRules() +131
OakLeaf.MM.Main.Business.mmBusinessObjectGeneric`1.CheckRules(mmBusinessObject businessObject, DataSet ds, String tableName) +169
OakLeaf.MM.Main.Business.mmBusinessObject.SaveDataSet(DataSet ds, String tableName, String databaseKey, IDbDataAdapter dbAdapter) +795
OakLeaf.MM.Main.Business.mmBusinessObject.SaveDataSet(DataSet ds, String tableName, String databaseKey) +101
OakLeaf.MM.Main.Business.mmBusinessObject.SaveDataSet(DataSet ds, String tableName) +159
OakLeaf.MM.Main.Business.mmBusinessObject.SaveDataSet(String tableName) +126
OakLeaf.MM.Main.Business.mmBusinessObject.SaveRow() +173
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform