My original reply to this message was eaten and finally kicked back. I have tried converting both the component and host system to v16, run MSC on both. the host, with an interpreted component crashes right to the desk top - no error.
Chip > Chip, > > Among the things that work differently compiled vs source code are: > RESOLVE POINTER($Var_p;$Var_t;$Tbl_i;$Fld_i) > > …which returns an uppercase VARIABLE NAME compiled, and a mix-case > Variable Name when source code. > > If using the result of RESOLVE POINTER as a Property Name, consider > uppercasing it. > > I had this problem….. > > David Ringsmuth > > From: Chip Scheide via 4D_Tech > Sent: Friday, October 11, 2019 4:07 PM > To: Tim Nevels > Cc: Chip Scheide; 4D iNug Technical > Subject: Re: stack error - again > > On Fri, 11 Oct 2019 15:48:39 -0500, Tim Nevels wrote: >> >> You said it only happens when you use one specific compiled component >> with one specific host database. > > actually its is not compiled component - it is the INTERPRETED version > of the component! > compile it and it works?!?!?!?! > > >> Why don’t you take 30 minutes and give it a try. >> Just copy over enough methods to make one shared >> component method available to the host. Compile >> that and install it in the host. > I did try a new version of the component and I get the same problem... > > what I am trying to avoid is a new host....100+ tables, 2200+ methods, > unknown number of forms, some with some very finicky object and maker > placements (reports). > > :) > > 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] > ********************************************************************** > ------------ Hell is other people Jean-Paul Sartre ********************************************************************** 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] **********************************************************************
