I thought about the problem a bit more and, even though I believe the behaviour to be a bug in webcombo (hey, it can't find a value that is definitely in the result set of the databind), I figured I would make it easy for the webcombo and only retrieve the actual record I needed.
This works (so far anyway). If the user uses the webcombo after the initial display then the InitializeDataSource will be raised and the result set selected this time is the entire set of values.
I guess another workaround would be to change the initial set retrieved (default 15 I think) to a large number (40,000 in this case to allow for growth) but this would mean a big performance hit.
Anyone else having similar problems?
Dave