Jerry,Never feel bad for asking a question! That's what a forum is about. Besides, this is a very valid question. The problem is that we have added some functionality in version 1.4 to support compound primary keys which in turn supports compound foreign keys. This means that each of the errors requires that the definition is an array instead of a string. To do this, the definition would be like this:
BusinessParentRelationship1.ForeignKeyField = New String() {"orit_or_pk"}
BusinessParentRelationship1.ParentBusinessObjectType = "StrataFrameSample.OrdersBO"
BusinessParentRelationship1.ParentPrimaryKeyField = New String() {"or_pk"}
Let me know if this doesn't clear things up. Also, the official 1.4 release will be released this week and the tutorials will be fixed as well. Sorry for any trouble this may have caused.