Ian,
>
>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.

You didn't have to do that just to add a field. You can always add a field manually in the Entity object.

>
>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?
>

I am not aware of a conversion for upgrading a project from MM2 to MM3.5 other than changing the references. I had some problems like this before and I created a new project from MM3.5 to give me classes like aBusinessObject that I could copy the code over to my project. I upgraded all my objects from one version to the next this way with good success.

I am not sure about your specific questions without looking but you might compare a fresh 3.5 project objects to your existing 2.0 objects.

Updated: I also just noticed your post again about converting your objects. Did you also change the framework version on the project from 2.0 to 3.5? Did you change all the mm references as well?

Tim