>>>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

Is not. Are.

>in a standard format; each edit provokes a full resend. ...

>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.

Map bigint to a n(19) in a view/SPT? Worth a try...