Hi All,

I have a web forms project that is currently using MM business objects to consume data from a SQL Server. Everything was working just fine until I needed to add a field to one of my table. I had been using legacy business objects from MM 2 up until this point. Now I needed to migrate my business objects to MM 3.5 in order to use the generator. Once I converted my objects to 3.5 two things happened.

1) The GetAllData began generating errors that claimed that dbo.[tablename] was not an object. I can code around this by using my own dynamic SQL statements, but it might be an indicator of a bigger issue.

2) All references to BO.SaveRow() began generating the error "Object reference not set to an instance of an object"

I have heard from other users that I know that using stored procedures from the BO generator works fine, but that they also had problems with the dynamis SQL statements. I would rather stay with the SQL statements if I could. Is there another setting or something that I must specify now when using version 3.5 or something else?

Thanks,
Ian Plunkett