>Colin,
>
>That didn't work either. I had already tried that one. I think my other option is to use two views one to list all records and one to edit on. That way way I can do a requery on the single record, but I'm still not sure if that will work either though because I won't know the key to use for the Parameterized view yet either.
IMO, forget about the 2 views idea. It's not needed and your just creating a maintenance headache for yourself.
This should work. A few questions:
After the TABLEUPDATE and REQUERY() are you refreshing the values with ThisForm.Refresh or similar?
Are you sure you have the correct alias SELECTed before the REFRESH()
Are you sure the stored procedure is actually running and the ID being created?
>
>However, another way might be to store the new value into an object property or look at the actual value that was posted by looking at the actual table since a VIEW always opens the actual table as well?
Trouble with this is, the base table is not necesarilly sitting on the same record as your view and if you don't know the ID value you can't find the record..
>
>HMMM!!!
>
>MAYBE???
Colin Magee
Team Leader, Systems Development
Metroland Media Group Ltd.
Mississauga, Ontario, Canada
cmagee@metroland.comNever mistake having a career with having a life.