Help!

I am having difficulty using the record update object.
I am following all the steps that I know about.

I have a search page with two fields one for Last Name
and the other for Logout where the user is prompted to enter "yes" if they want to logout. I have a recordset that resides on my results page since I have a multifield search I have written the following SQL script to retreive the record:

SELECT TOP 1 LAST_NAME, FIRST_NAME
FROM LOG
WHERE LAST_NAME = 'MMColParam' AND LOGOUT <> 'MMColParam'

Then I have placed a record update object on the results page. The Logout column is to be updated in my table. I am not sure what to enter for unique key ID. The Logout column, Last Name Column or the generic numeric ID column
given in My MS Access Database (Help suggests using the latter). I have tried all three.

The error I recieve when I try it all out says that there is something wrong with the page requested. What could be the problem

Create a filed called ID or something like that! set it to INT and have it autonumber, then you can target your ID as UNIQUE, and all will work

I have a ID column it is called logID. It was already set to autonumber and long interger. When I set the unique key to ID column (renamed ID or not) I an error that says "Please choose a unique key from the selected record set, or click cancel. What am I doing? wrong?

I have a ID column it is called logID. It was already set to autonumber and long interger. When I set the unique key to ID column (renamed ID or not) I an error that says "Please choose a unique key from the selected record set, or click cancel. What am I doing? wrong?


<BLOCKQUOTE id=quote><font size=1 face="Verdana, Arial, Helvetica" id=quote>quote:<hr height=1 noshade id=quote>
Create a filed called ID or something like that! set it to INT and have it autonumber, then you can target your ID as UNIQUE, and all will work
<hr height=1 noshade id=quote></BLOCKQUOTE id=quote></font id=quote><font face="Verdana, Arial, Helvetica" size=2 id=quote>

For anyone searching for the same issue, I resolved it by removing and recreating the affected recordset.

Thanks,
Matt