I would suggest contacting 4D Tech Support.

Dani

> On Oct 11, 2019, at 10:56 AM, Chip Scheide via 4D_Tech <[email protected]> 
> wrote:
> 
> In addition to the previous attempts to track this problem down.
> I have recently done the following:
> - examined all forms (both host and component) for recursive calls to 
> their respective form methods (which are project methods). - no 
> recursion found
> - insured that all host methods are NOT shared with the component. to 
> avoid host calling component calling host loops.
> - added* TRACE as the first (or last) line of code in ALL 3500 methods 
> and object scripts
> - added* ALERT(Current Method Name) as first (or last) line of code to 
> all 800 methods and object scripts
> 
> * - done by code, every method *should* have 2 Cr in the comment 
> header, but in case there is code that does not have this the 
> additional line of code (above) was added at the end of the method.
> 
> even after all of this...
> Starting the Host (interpreted) with the interpreted component results 
> in a stack over flow error ---BEFORE--- and of the above traces or 
> alerts fire.
> The Stack error occurs After login (4D user login system) and after the 
> base 4D splash screen opens, but as indicate just above ---BEFORE--- 
> any code in either component or host runs.
> 
> Anyone have any other ideas?!?!?!?!
> 
> Thanks
> Chip
> 
> We have done so much, with so little, for so long;
> We are now qualified to anything with nothing <sigh>
>  - unknown
> **********************************************************************
> 4D Internet Users Group (4D iNUG)
> Archive:  http://lists.4d.com/archives.html
> Options: https://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:[email protected]
> **********************************************************************

**********************************************************************
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[email protected]
**********************************************************************

Reply via email to