Kevin,

Thanks for the response. I've already created a different binding scenario with my 2 custom user controls, where the control itself sets up it's own binding based on properties in the property sheet. I wrote an interface for this binding, and there's an method in our derived base business form class that tells all controls with this interface to bind themselves at the appropriate time (when I know that the business objects are there and they've pulled their data from the server).

So, the point is that I didn't go back and implement the change you suggested, but from looking at it, I'm pretty sure that it will work.

Now I'm working on a DataPicker control that can handle System.DBNull. The .Net DateTimePicker works fine with intitialized dates, but when adding new records, and there's date columns in the dataset that do not get intialized to a specific date, that control blows up trying to bind. I miss VFP's empty date, which I guess SQL doesn't have. Any suggestions there?

Thanks,

-Nate