Hey David, Right, CALL FORM will fix a lot of work-arounds needed for previous 4D versions. But my goal here is to have a single stable code base in 15 until making the move to version 16. I don't want to maintain two versions if I can avoid it. That said, I already have some v16 features embedded in specially encoded comments where I can easily activate the changes after the conversion from 15.
John DeSoi, Ph.D. > On Oct 10, 2017, at 8:13 AM, David Adams via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > Hey John, if you still need to fix what you described, CALL FORM ought to > work. Just past what method you want to run and the target window's form > will run it through EXECUTE for you. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
