Hi PB users,
We are facing a strange behavior with deployment of our PB2019R2 application (KTP).
On some laptop, in our login window, the code seems to try to close the window after open.
When we activate /PBDEBUG (parameter after .exe file) the problem disappear.
This almost the same old login window we used with all PB versions, working properly in 11.5,12.5 and 2017.
There is open event (pbm_open) posting a custom event by "this.PostEvent("init_fenetre")".
In the "init_fenetre" event the user choose an .ini file, some variable and transactions are initialized and there is a test on commandParm() parameters.
parametres = CommandParm ()
parametres = Trim (parametres)
IF parametres = "" AND sle_user.Text = "/" THEN PostEvent (pb_connect, Clicked!)
IF parametres = "" THEN RETURN
The only way to trace is to insert messagebox and recompil and reproduce on laptop with the issue.
Here is the conclusion :
After the RETURN, instead of staying on the window, the code is firing a close event, in which there is an HALT CLOSE just after an error message "Transaction not connect".
The PC with the issue on deployed application, are working in IDE mode and /PBDEBUG mode.
For now this version is not deployed to client's environments, but we are sure some of them will have the issue.
We need help to understand where is the problem. We check DLL, .NET, Visual C++ Redist, ... etc without founding a difference between the Laptops OK and those which have the issue.
Do you have any idea on what we do to correct this? We don't have any more :(
Best Regards,
Pierre
