Thomas

I'm going to give the record number dance a try in my test here, just to see what happens. To me, it's not a matter of getting the job done - it's an overall system architechture issue. I'm trying to avoid table/record specific coding and go exclusively with views, local or remote.

From everything I've read, poked through and played with this technique *should* work. In fact, if you close the underlying table just before running the table update, it DOES work. If you run the same code using a remote view, it works. Using local views, if you set a breakpoint after the requery(), bring up the underlying table in the debugger and scroll to the field it's refreshed and will work just fine when you continue.

I've been searching for the missing setting that will magically make this technique work, but I think we've dug up a bug here.

Thanks for the input - it's appreciated!