On Fri, 11 Oct 2019 16:25:55 -0500, Tim Nevels wrote: > On Oct 11, 2019, at 4:07 PM, Chip Scheide <[email protected]> wrote: > >> actually its is not compiled component - it is the INTERPRETED version >> of the component! >> compile it and it works?!?!?!?! > > Thanks for the clarification, I thought this was a compiler issue. > > Since it is an interpreted only issue, I’ve got more ideas. > > In the host database: > > At the first line of the "On Startup" Database Method put in a > TRACE. Do you hit this before the stack overflow? > At the first line of the “On Host Database Event” Database Method > put in a TRACE. Do you hit this before the stack overflow? as I stated in the start of this thread - I inserted a TRACE (in the host) and an ALERT(CURRENT METHOD NAME) in the component, as the first lines of code. Into EVERY SINGLE METHOD that already has code. which includes ON Startup, and ON Before ON Startup
The stack error occurs BEFORE any of this is hit. The reason I inserted the code into every method is i was working on a different system, and I have a form which is the only form for the table, and is set as Input and Output - but it is an entry form and so is not really happy being an output form. During startup of this system (no password, no On Startup) I was getting errors from this form -- even though it was not being displayed. > In the component database: > > At the first line of the "On Startup" Database Method put in a > TRACE. Do you hit this before the stack overflow? > At the first line of the “On Host Database Event” Database Method > put in a TRACE. Do you hit this before the stack overflow? > > There are the only 2 entry points that can run when you start a 4D > database. It calls “On Startup” in the host and it can call “On > Host Database Event” in the component. That is if you have the “ > Execute ‘On Host Database Event’ method in components” Database > Settings -> Security setting turned on in the host. > > You might also try turning that off if you have it on and see if that > makes a difference. the ON BEFORE STARTUP went was initially off when this problem first occurred. > If you never get to the TRACE command before you get the stack > overflow error, then it’s a real puzzler. yes -- hence the long and related postings look for ideas and/or answers :) > Could the host be really, really old and upgraded through very old > versions of 4D? Wasn’t there a compatibility setting from a long > time ago when the “On Startup” database method was first introduced > that would actually automatically call a method named “Startup” or > “Debut”? Could that be involved in this strange problem? The original of this system was written in v11, however during the move to v13 I did what I am trying to avoid now, and had to build a new structure, so this system is a v13 system. And btw, it basically passed 4D's 64 bit testing report. a few PICTS, a plugin (now updated) but that was all that failed. Chip > Tim > > ***************************************** > Tim Nevels > Innovative Solutions > 785-749-3444 > [email protected] > ***************************************** > > 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] **********************************************************************
