Hi Everyone,
I have a very weird Impromptu problem. I can open and run reports on Impromptu (User or Admin) v 7.1.724.0, but when I go to close the application (either by clicking on the X to close the app, or by choosing file--> exit), I have to do it twice to close off the app.
So, if I have a report open, and choose file --> exit, the first time, the report and catalog closes, but the app remains open, and choosing file --> exit the second time, the entire application closes.
Alternatively, if I have a report open and choose file --> close, the report closes (as it should), and then I still have to use file --> exit twice to close the application.
Does anyone have any ideas on how to resolve this? Its causing me a load of grief, particulary with scheduled report runs as the processes are still remaining open doe to the need to close the applicaiton twice (I should note that already the scheduled items are being called through a macro that opens and closes the imp application)
J
JGirl
Can you be clearer in your explanation.
Are you having this problem after the scheduled job completes.
If so look at the macro and make sure that 'IMPAPP.QUIT' is the last statement to execute whether in the normal execution path or the errorhandler routine.
NKT
cognosfreelancer, thanks for your reply.....
I can't really be too much clearer in the explanation because I don't know what is causing this problem, but:
- the imp application only needs to be closed twice by the user when using certain catalogs
- the macros run fine when calling reports using catalogs that arent causing the above error
- the macros leave a process running after quitting the imp application for catalogs that are making the imp application be closed twice
- this problem is occurring on multiple desktops and environments for the given catalogs, so it isnt an installation problem.
So, the problem is not with the macros themselves, rather it is with the impromptu application, but .... the impact of the problem with the application is being experienced when running macros - the users have gotten used to choosing file-->exit twice from within the app, but it is still a problem when being called from a macro.
My suspicion is that the impromptu catalog is semi-corrupt, but i need some ideas and was hoping someone else had stumbled across this before.
J
Perhaps you could call a third party application (like pskill) to terminate the application, at the os level. For example, we have a "Terminator" process running on our servers that terminates long running "impserver.exe" processes. You could similarly shell out to a batch process that kills the imp. application exe.
good luck.
cheers,
DW