L
Larry Reed
Guest
Matt, Thanks for the response and the explanation of the ghost window. I'm hoping someone else in the community that hast figured something out. I would prefer to be able to deal with what happens when a user clicks on the x when a synchronous appserver session is running. It's a bit of work and redesign to switch to async appservers. And without support for dataset we're running into issues putting the dataset into a longchar with a codepage conversions combination of 1252 on the client and ISO8859-1 on the agents/database. One bad character in the database is causing the process to blow up. This is from an open ticket I have with Progress Tech Support. I don't particularly care if the character doesn't display properly but I do care if the process blows up. The recommendation is to clean up the bad characters and convert to utf-8. Quite an undertaking with 600 + databases (190 or so transaction db's). And an existing application (based on Xponent) that would need to be re-certified with the new code page. Not something I had planned on doing. We are 2.25 years into developing a new application using .net for GUI. And have yet to deploy anything. We are currently using progress 11.5.1.011 64bit which I believe is close to the latest. And would like to be able to deal with what happens when a user clicks on the x when a synchronous appserver process is running. Any help from Anyone would be appreciated. Thanks, Larry
Continue reading...
Continue reading...