If you are having trouble with generating your objects and stored procedures because of the schema bug in MyGen, you can now download the BETA of the next version that fixes this problem. I highly recommend you update, but be aware that this is beta software, so there may be other problems to iron out before a release.

My initial test shows that the schema problem has been fixed. You can download the beta here:
http://www.mygenerationsoftware.com/phpbb2/viewtopic.php?t=2039

I just love it when my ISP just goes down for no reason every spring. I gotta get me a better hosting environment... 

Just wanted to let you all know that a bug has been reported in the SQL DAAB Stored Procedures template. If a table resides in a schema other than dbo, the generated stored procedures will not work properly. This is most noticeable if you are using the AdventureWorks sample database from Microsoft.

I have just posted a fix to the template on the MyGeneration site. You can download it using the built-in template update mechanism inside MyGeneration.

However, you should also know that there is currently a bug in MyGeneration when reading tables not residing in the dbo schema. MyMeta will incorrectly report IDENTITY columns as IsAutoKey = False, and so the Insert stored procedure is not properly generated. The MyGen folks are aware of this bug, and it should be fixed in the next maintenance release. The only current workaround is to script the table to the dbo schema and then generate the procs and business objects. You'll also have to set the SchemaTableView property to the correct schema.

Post a note on the MyGeneration forums if you have any questions or problems.