>Tim,
>
>>There appears to be a new property in the Business Object called PhysicalDbcObjectName which is seperate from the TableName property. When I generate new business objects for Sql server the table name property is filled with the table name such as "Customer" but the PhysicalDbcObjectName property is filled with "dbo.Customer". I am using SQL server 2005.
>>
>>This has turned out to cause me a problem as I get an "Invalid Object Name dbo.Customer" unhandled exception in the adapter.Fill call within the DataAccessSQL class. The business object generator works just fine however. Has anyone else experienced this? Once I removed the "dbo." from the property it worked fine.
>>Thanks
>>Tim
>>
>>Updated: I should also note that if this property is left blank the TableName property is used instead. These are used for the SQL statements.
>
>We've actually had this property for several versions now. Can you post the full stack trace an error?
>
>Best Regards,

Hmm.. Maybe I will look at the when this property is created and used. Looking back at my 2.4 projects the property isn't in any of my business objects created against the same SQL Server. In my 3.5 project if I just remove the "dbo." from the front of the value it works just fine. I can re-create the problem and get the stack trace.
Tim