Charlie: Yup, that *would* work fine "if your forms names provide indications to the forms purpose."
IIRC, I hit this issue in a V13 app and the form names were not consistent so I had to create a workaround (which I can't find at the moment). -- Douglas von Roeder 949-336-2902 On Tue, Nov 8, 2016 at 1:57 PM, Charlie Vass <[email protected]> wrote: > Doug, > > Would the command "Current form name” <http://doc.4d.com/4Dv15R5/4D/ > 15-R5/Current-form-name.301-2936476.en.html> be of assist? That is if > your forms names provide indications to the forms purpose. > > Charlie Vass > 4D TS > > On Nov 8, 2016, at 2:48 PM, Douglas von Roeder <[email protected] > <mailto:[email protected]>> wrote: > > I'll vote for that feature request if you create it. I recently hit a > situation similar to what Kirk is facing and the only option was some > pretty clunky code. > > ********************************************************************** > 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:[email protected] > ********************************************************************** > ********************************************************************** 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:[email protected] **********************************************************************
