You can't do that

[John Esak]

> John,
> >
> > Think of what he is saying as header and detail
> > records.  He wants to insure
> > that there is a header record for all associated
> > detail records, I think.
> >
>
> Exactly.
>
> > Now, I consider this a programmers responsibility.
> > However, one would need to
> > turn "break off" to keep someone from canceling out
> > of a routine prior to the
> > header record being created.
>
> Or just make sure the header record gets written
> before you give the user the opportunity to add
> detail.
>

Okay, it's just that I have NEVER, not even once run into a situation where
there are child records with NO header record. I think if that happens,
there is something improperly written.  However, I have heard of this
happening to others who are the best filePro programmers I know... so, I
suppose I must grant that it can happen somehow even to the best of us.
Just haven't ever seen it yet. So, implementing code to ensure that it never
happens, when it never has... is sort of silly to me. At least, there are
hundreds of things I'd rather see in filePro first.

John