>I had the same problem last week, with the only work around I found being
>to change the index to regular, and putting some checking code in valid
>for the field. If the code returns a .F., the user gets a wait window
>and the cmdSave is not enabled.

I'm experimenting with some code in the record validate at the moment. Seems to me that if it turns up false, the save won't happen, and I could bypass the error message. Kinda defeats the purpose of the Candidate key, though. Your way of using the field valid seems interesting because you have the option of changing the message. That way also seems better than trapping the error when it occurs. Do you have to turn your key into Regular, though? I guess the question is moot; you have to code around it anyway.

Yes, we're using buffering. I can't imagine not using it. There would have to be some pretty compelling reasons not to, I think.

Steve