This can be demonstrated when launching a form from ebase designer, then immediately launching the form a second time without closing down the browser. When tabbing back to the first form session/tab, the ebase session returns: The application has timed out. Press the browser's refresh key to start again as soon as any interaction is attempted.
This is not what happens in ebase 3.4 designer, where both session tabs remain operational and independent of each other.
I've searched the forums and found a help page that appears to be related: /ufs/doc/multi_session_support.htm but I don't understand what, if anything, I can do to configure ebase to remedy the issue.
This is a real problem for us as our users need to have 2 or more ebase sessions running concurrently to be efficient in their work. I'm guessing the problem is something to do with how our ebase sessions are launched - which is from an unrelated IE window - however, we don't have this issue with ebase 3.4 - it's just ebase 4.5.5.
Any help or pointers would be greatly appreciated
