>Hi Tim,
>
>Thanks for the added detail. Not sure I'll be much help, but hopefully others can be.
>
>I've not had the pleasure of a Win95 client but recollect mention of some problems there, more to do with locking I think (than "lost" records).
>
>I have heard of strange things happening on NT Server when heavy printing is going on. Things like random 'not finding/opening of index file' yet no error regarding (problem found later when index use attempted). There were other anomalies too. It was Barbara Paltiel (often on UT) who experienced these oddities and I recollect that she got around most by getting agreement to keep printing low while app ran.
>
>It sure wouldn't hurt to code the alias in your TableUpdate command, just to be certain of things. I also assume that you are checking the return from TableUpdate to confirm success.

Just looking over this thread...this reminds me a little of the recent problem I had where sometimes an entire server table was pulled onto the local machine, and all the Tableupdates were done locally. Then there was a network problem, and the server table never got updated with anything...

Does this bear any resemblence?