OK, Tom. Still not sure what it is you're doing, but it sounds like you've got a handle on it more or less.

>>By the way thank you for your fast response! I appreciate that.

You're welcome, although it doesn't appear that I've helped very much. <g>

~~Bonnie


>Bonnie;
>
>I am manually setting up the UPDATE command.
>
>Here is what I have found on Google.com
>
>1. From Microsoft - this is a known bug in SQL Server 7.0. Use SP 2 to resolve the problem. We are using SQL Server 2000.
>
>2. Temporarily disable Foreign Key Constraint using NOCHECK CONSTRAINT. That did not work.
>
>I will try a few other things and see what I come up with. Thank you for your input so far as it gave me a concept that may resolve the issue. I will simply use a Drop Down List and hope that it works like VFP. I might run into a bit of a problem getting that to work, as I want to display the value assigned to the column while allowing the user to choose a valid value from the second table. Does that make sense even fro a Friday morning? :)
>
>By the way thank you for your fast response! I appreciate that.
>
>Tom
>
>
>
>
>>Tom,
>>
>>>>Let me say that I understand what the error means and I am requesting suggestions about how to resolve it. I tried Google and did not find a solution.<
>>
>>I hoped that you understood what the error was, but what kind of generic solution are you looking for? How are you updating the table? Is this in a Stored Procedure? Have you manually set up the Update Command or are you using CommandBuilder? I don't think a "generic" solution applies to this problem, at least not with more information about how you are doing this.
>>
>>~~Bonnie