IW10 open IW14 Form (dll)

[alex.trejo@tttnet.com.mx]

It is not advisable to try to mix into a single binary. You could however have 2 applications that use URLs to pass control back and forth and share state via session info in a database.

thanks for the prompt reply. I have begun testing that scenario. In IW10 calling URL of IW14 app with coded parameter string (form to open, logged user), in IW14 in SC defined vMainForm and logged user from decoded parameter. Is this the best approach? Or how to "pass control back and forth"?

The reason I wanted to include an external IW14 dll is to have the same feel for user when entering and exiting a form (stay on same browser window). With new approach (URL to new app), browser opens new tab with IW14 form, and when "returning" (WebApplication.Terminate with its variants I get either error o stuck in an external webpage) I just want to have the new form closed and control back in calling IW10 form. Is this possible?

UPDATE: In the "RETURN" button in the IW14 form with  AddToInitProc('window.close();') I can close the browser tab/window, leaving the calling IW10 again active.

Best regards,

Could you please elaborate on the "pass control back and forth and sharing of state via session info"?

What I accomplished thus far is pass control from IW10 entry app via NewWindow(URLofIW14app_withParams). And when in the IW14 form the user hits "Return" I close the tab. I don't know how to keep the SessionTimeOut from expiring in IW10 entry app if user is working on IW14 app longer, and how to pass control back other than closing the IW14 app & browser window.

Thanks