>>Hmmm, here my machine tending instincts disagree. IMO it should NOT depend on "full data afresh", but conscious decision on table usage or needs.
Data is passed in a standard format; each edit provokes a full resend. Receiving (my) end processes what it receives. A more recent receiving interface checks parent and 1:1 rows for value change and documents for the benefit of the human operator if (for example) the data changes after bill dropped- but not the 1-M data that is highly variable.
>>So you depend somewhere on vfp to get next key ? Why ?
No, on the SQL Server identity field. As 2B approaches, the INT identity could be expanded to bigint, if VFP handled that. I have not yet explored the feasibility/performance of VFP floating point or Double precision field type for backend bigint identity.
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1
