J.M.,
Could the calling command file check for orphan rows on exit from
the form and do inserts as needed? You could do it from a row exit
eep on the primary table, but I'm not certain the insert would occur
in a way that would actually work for you.
Ben Petersen
On 15 May 2001, at 9:26, J.M. GRATIAS wrote:
>
> Hi all,
>
> I have a 2 tables form used in both ENTER and EDIT USING mode.
>
> Primary table use no tiers and columns are spreaded on 2 pages.
>
> Secondary table can have severals rows linked to the same primary row, and
> at least one.
> A tiers is set to display severals rows on the same screen.
>
> I need to insure that, after adding a primary row, user can't exit the
> form without adding at least one secondary row.
>
> I other way, I don't want to have orphan primary row ...
>
> As I am not familiar with triggers, I try to do that trhu EEP, without any
> success.
>
> Any idea to help putting me in the rigth direction ?
>
> TIA,
>
