Hello Mark,
thank you very much for your reply.
After we installed SDT, we looked in the MM's Developers Guide to see what should be done with the MM's project to work with SDT and we did everything. Now all SDT classes instantiated when app is running. I assumed that everything should work correctly without modifying anything unless I am calling SDT methods programmatically. Maybe I am missing something? If I'll use your advise that means that I am going instantiate DBCXMgr one more time, since it was instantiated already by framework, correct? I would expect that we will set some property and it would do everything itself.
So the simpliest way for us was to set DBCXMgr's Datasession to Default and everything works fine since now oMeta.ooSDTMgr can find our database where it's open. What do you think about it?
What I don't understand is the following code in cStonefield's Init()
(sorry for displaying code like that. For some reason the "pretty" thing I used before doesn't work anymore???):

IF THIS.OpenDefaultDatabase()
IF THIS.PARENT.oMeta.oSDTMgr.NeedUpdate()
THIS.PARENT.oMeta.oSDTMgr.UPDATE()
ENDIF
THIS.CloseDefaultDatabase()
ENDIF


The THIS.OpenDefaultDatabase() works fine because cStonefield is instantiated in the default datasession, it opens current database, no problem. But THIS.PARENT.oMeta.oSDTMgr.NeedUpdate() jumps to the private datasession and there is no way it can find current database unless I will modify something. It almost looks like a bug in MM(GOD forgive me for criticizing MM and Kevin! I hope he won't read this posting.), unless I am missing something obvious which is possible.
What do you think?
Regards
Igor