Access and SQL Server #deleted# problem

[dan08]

I have a finance database in Microsoft SQL Server and I am constructing a front end in Access. I am building a check request form that allows people to enter new check requests and also lets them browse through past requests. I created a function in SQL Server that gets the users username and created a view that selects only the requests entered by that user. The problem comes when a user enters a new check request. If the username doesn't match then I get #deleted# in all the form fields because the record is now out of the view (but it is getting added into the finance table). I am able to overcome this by locking down the username so it cannot be changed. But I would like a better fix. I there a way to keep the recently added records visible at least until the form is closed and reopened?

 

[lameid]

The only thought coming to my mind is to bind the form to a disconnected recordset and then batch update by reconnecting the recordset...

A more practical approach may be to make a batch entry system so that you enter batches of checks or documents and then post the batch to the final table... then you can have the batch owner able to see his unprocessed bath instead of his own documents. Then with the batch history, you would see who entered it and who owns it.