>It occurred to me recently that a DataSession property would make more sense, or as much sense, as it does for a form class.
>
>Is this nutty?

Sort of. It seems they were partially out for lunch when they were designing it - instead of it having its own DataSessionID (and DataSession) properties, form has them. This poor class was designed to live only as a special object on a form, never on its own... sort of a permanent child, never to grow up.

Today, almost ten years after the fact, we'd all like to have this beast redone, but too late now. What I'd like to see would be a cross between a Session and Datasession class, i.e. something that could be just dropped on a form and that would have the good behaviors of both of these classes. Seems to be a bit too late for that now, unless we rolled our own.