I'm running into a case where a business object's SaveDataSet() is trying to insert into a table other than the one set in the business object's TableName property. This is ocurring in an Outlook 2003 Addin developed under VSTO2005 ... and appears to occur only when "deployed"; I do NOT see it occurring on the development machine. I've run a SQL Profiler trace, and it indicates that the Insert command being sent to the DB is for a different, but similarly-named table, which itself had just been added to for the first time.

Anyone else seeing anything like this?