[Migrated content. Thread originally posted on 20 October 2005]

Has anyone encountered the following error message or know what it means:

ACCEPT recusion limit reached!
Further execution may cause unpredictable recults

This typically happens when you have several nested accepts within events.
Like;

ACCEPT SCREEN1
  EVENT PROCEDURE
    ACCEPT SCREEN2
     EVENT PROCEDURE
       ACCEPT SCREEN3
         ...


You should not launch new accepts within events.

---

[Migrated content. Thread originally posted on 20 October 2005]

Has anyone encountered the following error message or know what it means:

ACCEPT recusion limit reached!
Further execution may cause unpredictable recults

OK, but what about this whole issue with multi threading.

We get this all the time, but we're not launching more accepts within accepts to my knowledge.

Menu program calls program X in a thread, program X runs quite happily, and at some point displays the recursion limit reached message.

So program X is in trouble, but so is every other program running including the menu program!
We've reproduced this fault in V7.0 (our customer has it on V6.1 approx 6 to 8 times a day).
The fault we've found in V7.0 seems to be more a case of do something 10 times(like click a button) and its away!

So, is it OK to do this?
Menu program is really a grid, and the GOTO-CELL-MOUSE is the trigger to call another program in a thread.

Shaun

---

[Migrated content. Thread originally posted on 20 October 2005]

Has anyone encountered the following error message or know what it means:

ACCEPT recusion limit reached!
Further execution may cause unpredictable recults

Only other thing would be this I suppose.

We've got a PERFORM Acu-Screen1-Routine

User does something which needs another screen to be displayed within the program, so PERFORM Acu-Screen2-Routine is executed.

Is this then going to potentially cause the recursion limit reached?

Shaun

---

[Migrated content. Thread originally posted on 20 October 2005]

Has anyone encountered the following error message or know what it means:

ACCEPT recusion limit reached!
Further execution may cause unpredictable recults

If the sub programs are called via an event procedure, then the original (1st) program is waiting on it's accept (the accept is not terminated by an event).

---

[Migrated content. Thread originally posted on 20 October 2005]

Has anyone encountered the following error message or know what it means:

ACCEPT recusion limit reached!
Further execution may cause unpredictable recults

There is a number of issues that can cause this situation. To address this, we will need to look at it through tech support.

---

[Migrated content. Thread originally posted on 20 October 2005]

Has anyone encountered the following error message or know what it means:

ACCEPT recusion limit reached!
Further execution may cause unpredictable recults

Originally posted by gforseth
There is a number of issues that can cause this situation. To address this, we will need to look at it through tech support.

I have raised it through support, i'm just curious regarding my example about about the Screen1-Routine/Screen2-Routine scenario.

Shaun

---

[Migrated content. Thread originally posted on 20 October 2005]

Has anyone encountered the following error message or know what it means:

ACCEPT recusion limit reached!
Further execution may cause unpredictable recults

I have the same problem with the version 7.0.
We use multi thread method but ONLY with AcuThin. After 10 times the application show the message.

These programs run correctly with the normal runtime.

:confused:

---

[Migrated content. Thread originally posted on 20 October 2005]

Has anyone encountered the following error message or know what it means:

ACCEPT recusion limit reached!
Further execution may cause unpredictable recults

We get it in V6.1.
Something was meant to be fixed in V7.0, but it just seemed to make things worse than before

Shaun

---

[Migrated content. Thread originally posted on 20 October 2005]

Has anyone encountered the following error message or know what it means:

ACCEPT recusion limit reached!
Further execution may cause unpredictable recults

We had this problem and there is an ECN that fixes one instance of the problem. I don't have the ECN number in front of me, but you might want to ask Tech Support to look for it.

Of course, the ECN that fixed my problem with this may not solve the problem you are having...

Rob

---

[Migrated content. Thread originally posted on 20 October 2005]

Has anyone encountered the following error message or know what it means:

ACCEPT recusion limit reached!
Further execution may cause unpredictable recults

I have also begun getting his message with runtime version 6.1. If I set the user back to version 5.2.1, the problem goes away every time.

It seems to occur more frequently as the user's computer or network becomes busy, and the user's input is quicker than the program can handle.

I was hoping the problem was fixed in 7.0, but evidently it's not.

---

[Migrated content. Thread originally posted on 20 October 2005]

Has anyone encountered the following error message or know what it means:

ACCEPT recusion limit reached!
Further execution may cause unpredictable recults

Look into ECN3314.

I'd imagine this will cure the majority of your messages, however some manual coding changes will have to be made to your code.
Especially if you use GOTO-CELL-MOUSE events within grids.

Shaun

---