Application is getting crashed

R

rash

Member
Progress 9.1E
Windows XP


Application is getting crashed.


I have to close the current active window & have to set login screen.
DEFINE VARIABLE hCurrWindow AS HANDLE NO-UNDO.


IF VALID-HANDLE(hCurrWindow) THEN
RUN CloseWindow IN hCurrWindow.


CloseWindow is defined in the program referenced by hCurrWindow as:


&ANALYZE-SUSPEND _UIB-CODE-BLOCK _PROCEDURE CloseWindow Dialog-Frame
PROCEDURE CloseWindow :


HIDE FRAME Dialog-Frame.
END PROCEDURE.


/* _UIB-CODE-BLOCK-END */
&ANALYZE-RESUME


The application getting crashed after reaching upto the Login Screen.
Eventhough it's not throwing an error but gettting restarted at this point.
 
I don't know about anyone else, but for me there's nowhere near enough to go on here.

Are you running the debugger? Are you stepping through to see exactly what's happening? Why are you hiding the frame? What does the login screen do? Does it maybe start a new dialog with the same name as the one that's hidden, not closed?
 
A user gets logged in with his credentials for doing sales(mainloginscreen.w).
Now suppose user want to select any product from product lookup(prodlkp.w),
& he has gone for tea, then screen should be locked(lockedscreen.w) after few inactive moments.
Then if some other user tries to unlock the screen then product lookup window
should be closed & he should be redirected into the main login screen(mainloginscreen.w).


CloseWindow procedure has been used to close product lookup(prodlkp.w) window.
 
The behavior you describe is like that of a STOP condition. A STOP condition - if not handled explicitly - will not necessarily create an error message, but it will re-run the first procedure in you session. Usually that happens if the application does not handle STOP conditions.

Probably this knowledge base article will shed some light on the behavior:
http://knowledgebase.progress.com/articles/Article/P107860
Click to expand...
Heavy Regards, RealHeavyDude.
 
You must log in or register to reply here.
Back
Top