OK, here is the situation. We have a stored proc that goes and collects a list of column names that the user has saved off as a personal view, then, it constructs a SQL statement to select those columns from the underlying table - only, in this case the underlying table is actually a view.
This works fine, all of the columns come back, but if you save the recordset as XML and you look at the attributes, some of the columns have rs:basetable and rs:basecolumn and some of the fields don't. - though, if you go through the fields collection, all of the fields do have proper names
This is a problem, as we're loading the recordset into the datasource of an Infragistics Ultragrid, and later we are trying to use the basecolumn which the Ultragrid keeps a reference to. So, the basecolumn ends up being '' for some of the columns.
My question is, what would influence whether these rs:basecolumn or basetable attributes are returned for a column?
There appear to be no differences between some fields that do return a basecolumn and some that do not (as far as how they are defined in the view, or referenced in the stored proc).