>Are you saying (strategywise) Control the cursors directly in a private datasession from the session object to keep things lite? The DE doesn't lose you that much except close tables, initialselected alias, etc.? What else would you lose?

That's my suggestion. This is all new to me too (SP3). IMHO, you don't lose anything, except the ability to adjust some cursor properties as objects. You lose DE.InitialSelectedAlias, but it takes just as much code to set that property as it doesx to SELECT that cursor anyway. Give your session class a method called OPenTables that opens all the tables you want, and then you can do that with one method call too. A session object cleans up after itslef too. When it is released, its private datasession is destroyed, and all tables in it are closed.


>Rick Strahl was wondering what memory requirements/resources were involved with this session object and what would occur when you have to time out on such.

I can't say this for sure, because I have not tested, but Calvin Hsia mentioned that this class is about as lightweight as they come. After all, it only has one property (DataSession).