Mike,

A simple question (of course, it's not your case, but just to check it): are you sure, you don't use buffering? Select SQL doesn't return new records from buffered table. Also after tableupdate, try flush. One additional trick: Clear memory (may or may not help).


>No Novell here. A variety of NT and 2000 networks.
>
>We just did a test with a VFP COM .dll writing a record to a table (on a remote server) and a stand-alone VFP .EXE application ON THE SAME MACHINE couldn't see the record until it was shut down and re-started.
>
>We put in a SELECT MYTABLE followed by a GO TOP just prior to the select and the problem was gone. Take it out and it's back.
>
>Trouble is it is very hard to reproduce. We'll hit a situation like this wehre it happens every time (on all machines). When we try to reproduce it in a simple envirionment so that we can nail it down, it won't happen.
>
>It does seem to be predominant in forms with private data sessions however, but I can't confirm that or anything else causes it.
>
>Mike