4D v6.7 implements the concept of inherited forms. You can create a form in one table that is used in other tables. This is an ideal way to create forms with standard buttons, for use by list and input forms. But how does your 4D code know which table the form is currently being called from, so that it can carry out operations on the correct selection of records? This technical note describes a simple way of managing some of the typical operations that might be
called from your form buttons.

Download Complete Tech Note & Example: Windows | Mac