Have you retreived the primary key in your recordset?

Have you read:
-http://support.microsoft.com/default.aspx?scid=kb;en-us;Q294842
-http://support.microsoft.com/default.aspx?scid=kb;en-us;Q300586
-http://support.microsoft.com/default.aspx?scid=kb;en-us;Q244136


>The following problem is driving me nuts. I have an app that opens up to a mult-tabbed SSTab control. One of the tabs allows the user to enter another screen to save follow-up entries. Here's where the issue is:
>
>If the user opens up the client for editing they can save changes no problem. If they choose to add a follow-up as well (the follow up opens and closes a separate recordset as part of it's process) and save no problem. But if they add and save a follow-up and then check/un-check a control on one of the other screens they get the following error when trying to save:
>
>Row cannot be located for updating. Some values may have been changed since it was last read.
>
>If the user changes a different control (say a combo box) instead of a check-box the error does not occur. I can't find any info about this error axcept something relating to ADODC (which I am not using). I am using bound controls in some areas though. Has anyone else ran across this error?