Trouble with several sessions and sesstings Options.Net in runtime
Trouble with several sessions and sesstings Options.Net in runtime
I have main form with session and MDI-child forms with child session
In design time Options.Net=True for all sessions (main and child)
In runtime Options.Net=False for main session
Then create child form, params of main session (connect string and Net) assign to child session
Then create child form, all existent sessions (main and child) are closed.
P.S. I send mail with test project to support
In design time Options.Net=True for all sessions (main and child)
In runtime Options.Net=False for main session
Then create child form, params of main session (connect string and Net) assign to child session
Then create child form, all existent sessions (main and child) are closed.
P.S. I send mail with test project to support
ODAC doesn't support two modes (Net and native) simultaneously, in previous ODAC versions if you change Net option state then all sessions in IDE change their Net state too, now we change this behaviour and you can set a different state of Net option to TOraSession objects, but it doesn't mean that you can use "Net" and "native" modes simultaneously. The feature to use different state of Net option at design-time was added for those users who want to load several projects in IDE, where some projects use Net option and the other don't.
I reproduced your problem with MDI application and different Net option settings.
The main cause of such ODAC behaviour is that it can't use Net and native connections simultaneously. When you create a new MDI child form, you implicitly create new NET session, so not all Net sessions are disconnected - that is your problem. As a decision of this problem I could suggest you to create MDI Child sessions at run-time.
The main cause of such ODAC behaviour is that it can't use Net and native connections simultaneously. When you create a new MDI child form, you implicitly create new NET session, so not all Net sessions are disconnected - that is your problem. As a decision of this problem I could suggest you to create MDI Child sessions at run-time.