I didn't have KeyLinks explicitly defined, but I had KeyLinksAutoDefine set
to True. I tried explicitly setting it, but I get the same error.

Actually, this brings up another question for me about KeyLinks:

My table has a 2-field primary key (customerid and barcode), and some other
fields. My query selects all of the fields, except customerid, which is in
the Where clause (I'm selecting all records for one customer). What would
I set KeyLinks to? Just barcode, or both customerid and barcode? If I put
both in, I get an exception saying the customerid is invalid, I presume
because customerid is not in the select list. I can set it to just
barcode, and it accepts it. Barcode doesn't uniquely identify the row in
the whole table (the same barcode could exist for another customer), but it
IS unique for this dataset (where customerid is specified in the where
clause). Could this be the source of my problem? Anything special I need
to do in this case?

-Joe

At 04:14 PM 12/8/2002 -0200, you wrote:

>Jos,
>
>This sounds as a keylinks problem.
>How is your keylinks setted?
>Also, there is a property called KeyRelation that can be used to say IBO
>which table is to update. But on simple queries as you described that is not
>necessary.