The easiest thing I can think of is if you have a detail dataset that only
shows a sub-set of rows. You may only ever have a unique ROWID value in any
given detail dataset for a single master record, but the ROWID value would
not be unique for all master rows and their detail records.

Thus, on the detail dataset you would need both the master record ID plus
the Row ID in order to uniquely identify the record "on the server" not just
in your buffered group of detail records.

HTH,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com

-- We may not have it all together --
-- But together we have it all --

----- Original Message -----
From: "Raymond Kennington" <raymondk@...>
To: "IBObjects" <ibobjects@yahoogroups.com>
Sent: Monday, October 07, 2002 8:44 AM
Subject: [IBO] GSG013. Uniqueness of a row on the server.


> "For any dataset, KeyLinks establishes the uniqueness of one row when
looking at the
> server."
>
> Would it be better to write this:
>
> "For any dataset, KeyLinks establishes the uniqueness of one row when
considering a table
> on the server."?
>
> If not, then please explain, for then I do not understand how uniqueness
of a row applies
> to a server when several tables can hold the same data.
> --
> Raymond Kennington
> Programming Solutions
> W2W Team B