You can't do that

[Jeff Harrison]

--- GCC <gccconsulting at comcast.net> wrote:

[snip]
> 
> 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.

> 
> Of course, how one writes their program also
> influences how one manages this
> problem.  And, that is the crux of the issue. 
> Having filePro "control" this
> functionality would greatly restrict how one writes
> their programs.  Again
> removing the flexibility inherent in filePro.
> 

You would only remove the flexibility where you wanted
it removed.  You would be free to add or remove the
constraints as you wish.  I'd even be willing to
conceed a PFCONSTRAINTS=OFF variable, so that the
limits could be overridden in code if needed. 
However, again, if you override your self imposed
constraints and the data gets corrupted, then shame on
you!

Jeff Harrison
jeffaharrison at yahoo.com

Author of JHExport and JHImport.  The easiest and
fastest ways to generate code for filePro exports and imports.

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com