🚀 go-pugleaf

On Fri, 13 Aug 1999 10:27:00 +0200, "PIQUOT J�r�me" <wolff@media-net.fr>
wrote:

>thanks for your reply but i do not perform equlity test. this exception
>happens while i call Provider ApplyUpdates.

Well,  depending on how you have your UpdateMode set,  you may be
performing an equality test that you do not realize you are.  If you have
the UpdateMode set to upWhereAll,  you will perform an equality test on
every field in the record...  By setting the UpdateMode to upWhereKey,  it
will perform the equality test on the key fields only,  and upWhereChanged
will only compare against the fields which were changed.  

For most instances,  upWhereKey is sufficient when your table has a unique
index or key field.  upWhereAll is overkill in those cases,  as the
key/index field guarantee uniqueness.  I am sure there is a valid reason
for upWhereChanged,  but I can not think of one right now... :)

If your table has a unique key/index,  and you do not use any of the field
types I mentioned earlier (Date/Time, Currency, Float, Double, etc) then
you can set the UpdateMode to upWhereKey and quite probably resolve your
problem...

Jerry Bloomfield (TeamB)
-- 
Jerry Bloomfield                                     JersWork@wwa.com
Proud Member of Borland's TeamB
"We'll do anything if you don't pay us."