Bug?: Merging 2 datasets raises System.IndexOutOfRange exception

From: Steven (Steven_at_discussions.microsoft.com)
Date: 11/23/04 

Date: Tue, 23 Nov 2004 01:55:05 -0800

I have 2 datasets, a Business Entity dataset (where I add a couple of
expression columns to fetch data from Parent tables) and a Data Access Layer
dataset (without the expression columns). First initial load of my Business
Entity dataset works fine. Then, when I try to fetch new data, I get a
System.IndexOutOfRange exception with the message "Cannot find column 16".
When I check the offending table in both datasets, they both have 13 columns.

Important note: Before I try to merge the latest DataAccessLayer dataset
into my BusinessEntity dataset, I clear my BusinessEntity dataset, and remove
the Expression columns. After merging the two datasets, I add the Expression
columns again.

What's going on here? This really seems like a bug in the Merge
functionality of ADO.NET. It seems that the Merge still thinks that the
expression columns are there, which explains the reference to "Cannot find
column 16". How come?