>I am wanting just that one record updated from the original source before I move to that record with Next/Prev, etc.

Nope. It ain't gonna happen. If you want to get the latest version of a record in a view, you're gonna have to requery the view. Period. That's why I said that you might have to redfine your view so that you restrict the WHERE filter to just the one record you are currently on - then you can requery it all you like and just get changes to the current record. However, this will negate the abilility to use navigational style pointer movement (previous/next/top/bottom) because you would only have a single record in the query. You would then have to use a dialog or similar to get the query value for the next record you want and then re-query with the new parameter value.

I'm with John on this. If you want to see changes to source tables, then use tables and not local views. However, your requirement will restrict you to tables. Even on a SQL back end, to refresh a record (that you yourself have not modified) in a view, you have to requery the view and get the latest version of the record. Even then, another user might commit newer changes to the data source record just milliseconds after you requery so, your still not guaranteed to get the latest version of the record. The only way is to use tables, then get a lock on the record whilst you save it back to the table. This is the only way to ensure you have the "latest" version of the record, until you release the lock, that it.

HTH