>Bob,
>
>I am working only with Local Views at the moment but am making provisions for the future with Remote Views.
>
>However, I am looking along the same lines in the Stored procedure as creating an object to store the last ID into and replacing my Local View.

Then, in both cases I think the best bet is to call the stored procedure manually to get the ID, populate it in the view, then do the tableupdate()... this will work with local and remote views.

I assume you need the ID so you can populate the FK of a child table. This would allow for that.

BOb