>Adding a cursor object to the DE after it has already opened its tables does nothing but add an object that you can reference later. Why do you want object references to these? The object don't give you much control anyway...
>>
>
>Thanks Erik, I working on a tool for myself. It has a single form. The form has an open table method that allows me to pick a specific table to work on from an open file dialog. It could be any table so it's not in the forms DE (at design-time the DE is empty). Once I've selected the file, I set the buffering on the file to optomistic table.
>
>My framework has methods to enumerate the cursors in the DE and build a collection. It also has methods for SaveData, RevertData, etc. these methods work with a CursorCollection that is built from the DE. (basically what you layed out).
>
>My problem is the CursorCollection is empty when the form loads. I'm thinking I can just add a the cursor to the DE at run-time and have a RefreshCursorCollection method. Now my SaveData/RevertData methods work.
>
>I had also thought about a AddDScursors method, that would add tables in the current DataSession to the CursorCollection. Thus elimating the need for the RefreshCursorCollection method.
>
>I guess what I'm really trying to do is add the ability to use either the DE or the DataSession for building the collection.
>
>I think I've got a handle on it now. Thanks for all the help.

If your forms use Provate Datasessions, and you don't have any other use for the collections, why not just use AUSED in your data handling functions? It doesn't care whether the cursors are in the DE or not. You can check the buffering setting with CURSORGETPROP instead of checking the cursor's buffering property...