>Hi!
>
>You should not make ANY logical sense for primary key. Otherwise you could quickly find self in situation when primary key is not unique. Primary key - is primary key, it should identify record in table and nothing else. Of course, if your table is so large that you're trying to remove everything extra...
>
>Anyway, did you tried to play with view's keys more as I suggested?
>
>>That's ok and I do setup my Home table that way but the MoveHistory file you can think of as like the line item table of an invioce. It is a foreign key type table and the primary index is a composite index. I can't give it a Primary Key as that makes no logical sense. See my problem?
>>
>>Terry
>>

That worked. I now know what the problem was. I tried using the multi key solution before and it failed. What I forgot was that the last time I tried it I had faild to close the view on exiting the form. So, when I restarted the form to test the fix I got an Update Conflict because I had multiple (exclusive) opens running. This caused me to think the multi key fix didn't work. Thanks for making me go back and try again. My concept of views is OK thank God. I just failed in my use of the Sceintific Principle (change only ONE thing at a time)!

Thanks so much for the help.

Terry