I guess this is the best approach, dig into the source and catch it "red handed"

Thanks

>Well, Glenn...
>
>I'm officially stumped. This sort of thing "just works" for us. Now, I know that doesn't help... so let me suggest something that *should* help
>
>Add a breakpoint at the top of this method in the mmWebBindingStrategyList object (it's in mmBindingStrategy.cs of the Web Forms solution):
>
>

>public static void BindData(ImmWebBindingList mmControl, mmBusinessObject bizObj,
>			bool bindBack, mmBusinessStateChangeEventArgs e)
>

>
>Pay attention to the logic paths the code takes, especially the part where it gets the bindingsource information and where it decides whether to use a view or a datatable. Hopefully, there will be a "eureka!" moment.
>
>---J
>
>>It is invariably displaying the first item in the list. The source DS for this control is derived from a stored procedure on the SQL Server as follows.
>>

>>' Returns a DataSet containing ONLY UNIQUE STATES
>>Public Function GetAllStates() As DataSet
>>  'Stored procdure has replaced this select statement
>>  'Return Me.GetDataSet("SELECT distinct state FROM Zipcodes order by state")
>>  Return Me.GetDataSet("GetAllStates", CommandType.StoredProcedure)
>>End Function
>>

>>
>>Thanks
>>>Glenn,