Skip to main content

[archive] program gets jammed running under thin client

  • July 15, 2009
  • 7 replies
  • 0 views
D

[Migrated content. Thread originally posted on 15 July 2009]

I encountered a problem with activating an event-procedure under thin client:
In this simple program the user selects some options to make a report, then clicks the ?print?button. While the program is busy making that report, the screen remains visible. When the user now clicks on a button which activates an event-procedure in the program (though the screen is not accepted at that time), the program seems to loose track and gets jammed.
When normally executing such a program, doing so (though not usefull, but it happens..) does not cause any problem; only when the program runs under thin client.
Is there an option or config-variable to prevent this? I wouldn't like to change all simular programs to destroy or inactivate the screen while the program is busy.

    7 replies

    D

    [Migrated content. Thread originally posted on 15 July 2009]

    I encountered a problem with activating an event-procedure under thin client:
    In this simple program the user selects some options to make a report, then clicks the ?print?button. While the program is busy making that report, the screen remains visible. When the user now clicks on a button which activates an event-procedure in the program (though the screen is not accepted at that time), the program seems to loose track and gets jammed.
    When normally executing such a program, doing so (though not usefull, but it happens..) does not cause any problem; only when the program runs under thin client.
    Is there an option or config-variable to prevent this? I wouldn't like to change all simular programs to destroy or inactivate the screen while the program is busy.
    There isn't a config variable for this. You have the option of before the call to the print to disable all controls on your screen and then re-enable them once the call completes.

    You should report your issue to Customer Care as there may be some fixes that solve the issue
    D

    [Migrated content. Thread originally posted on 15 July 2009]

    I encountered a problem with activating an event-procedure under thin client:
    In this simple program the user selects some options to make a report, then clicks the ?print?button. While the program is busy making that report, the screen remains visible. When the user now clicks on a button which activates an event-procedure in the program (though the screen is not accepted at that time), the program seems to loose track and gets jammed.
    When normally executing such a program, doing so (though not usefull, but it happens..) does not cause any problem; only when the program runs under thin client.
    Is there an option or config-variable to prevent this? I wouldn't like to change all simular programs to destroy or inactivate the screen while the program is busy.
    thank you Dilbert for your reaction,
    I will do so (send an Email; would it be correct to send it to nesupport@acucorp.com?), but I hoped to get a solution without changing these kind of programs.
    D

    [Migrated content. Thread originally posted on 15 July 2009]

    I encountered a problem with activating an event-procedure under thin client:
    In this simple program the user selects some options to make a report, then clicks the ?print?button. While the program is busy making that report, the screen remains visible. When the user now clicks on a button which activates an event-procedure in the program (though the screen is not accepted at that time), the program seems to loose track and gets jammed.
    When normally executing such a program, doing so (though not usefull, but it happens..) does not cause any problem; only when the program runs under thin client.
    Is there an option or config-variable to prevent this? I wouldn't like to change all simular programs to destroy or inactivate the screen while the program is busy.
    thank you Dilbert for your reaction,
    I will do so (send an Email; would it be correct to send it to nesupport@acucorp.com?), but I hoped to get a solution without changing these kind of programs.
    D

    [Migrated content. Thread originally posted on 15 July 2009]

    I encountered a problem with activating an event-procedure under thin client:
    In this simple program the user selects some options to make a report, then clicks the ?print?button. While the program is busy making that report, the screen remains visible. When the user now clicks on a button which activates an event-procedure in the program (though the screen is not accepted at that time), the program seems to loose track and gets jammed.
    When normally executing such a program, doing so (though not usefull, but it happens..) does not cause any problem; only when the program runs under thin client.
    Is there an option or config-variable to prevent this? I wouldn't like to change all simular programs to destroy or inactivate the screen while the program is busy.
    It's been my experience that it is a good idea to disable controls if you don't want to get events back from them as Dilbert suggested.
    D

    [Migrated content. Thread originally posted on 15 July 2009]

    I encountered a problem with activating an event-procedure under thin client:
    In this simple program the user selects some options to make a report, then clicks the ?print?button. While the program is busy making that report, the screen remains visible. When the user now clicks on a button which activates an event-procedure in the program (though the screen is not accepted at that time), the program seems to loose track and gets jammed.
    When normally executing such a program, doing so (though not usefull, but it happens..) does not cause any problem; only when the program runs under thin client.
    Is there an option or config-variable to prevent this? I wouldn't like to change all simular programs to destroy or inactivate the screen while the program is busy.
    We've been down this road too.
    My own experience is that the "click" should be an EX-CMD-CLICKED and not an EV-CMD-CLICKED and disable the controls also.

    Also, depending on what your program is doing i.e. how long it takes to finish you might want to think about some sort of progress indicator working in a thread.
    This will nearly guarantee that your program won't as you describe lockup/jam or in my case show a "Remote host has stopped responding"
    D

    [Migrated content. Thread originally posted on 15 July 2009]

    I encountered a problem with activating an event-procedure under thin client:
    In this simple program the user selects some options to make a report, then clicks the ?print?button. While the program is busy making that report, the screen remains visible. When the user now clicks on a button which activates an event-procedure in the program (though the screen is not accepted at that time), the program seems to loose track and gets jammed.
    When normally executing such a program, doing so (though not usefull, but it happens..) does not cause any problem; only when the program runs under thin client.
    Is there an option or config-variable to prevent this? I wouldn't like to change all simular programs to destroy or inactivate the screen while the program is busy.
    We do as Shaun has suggested - always show a progress bar with a 'STOP' button that runs is a separate thread whenever there is a possible long time for collection of data for grids/lists etc. The only time this doesn't help is if a call to C$SYSTEM is in progress as this also suspends the other threads in the run unit including the progress thread (really annoying behaviour). I have attached a sample where a large amount of data movements are collected - all buttons and events etc. are captured in the other thread showing the progress bar.
    1 Attachments
    D

    [Migrated content. Thread originally posted on 15 July 2009]

    I encountered a problem with activating an event-procedure under thin client:
    In this simple program the user selects some options to make a report, then clicks the ?print?button. While the program is busy making that report, the screen remains visible. When the user now clicks on a button which activates an event-procedure in the program (though the screen is not accepted at that time), the program seems to loose track and gets jammed.
    When normally executing such a program, doing so (though not usefull, but it happens..) does not cause any problem; only when the program runs under thin client.
    Is there an option or config-variable to prevent this? I wouldn't like to change all simular programs to destroy or inactivate the screen while the program is busy.
    We do as Shaun has suggested - always show a progress bar with a 'STOP' button that runs is a separate thread whenever there is a possible long time for collection of data for grids/lists etc. The only time this doesn't help is if a call to C$SYSTEM is in progress as this also suspends the other threads in the run unit including the progress thread (really annoying behaviour). I have attached a sample where a large amount of data movements are collected - all buttons and events etc. are captured in the other thread showing the progress bar.
    1 Attachments

    Recent badge winners

    Explore all badges
    Terms & ConditionsAccessibility statement