I tested your suggested code and there is no change in behavior.

The only thing that reliably fixes this problem is to close the soitems table and reopen it prior to the SQL-Select statement.

use in soitems
use soitems in 0 shared

select sohead.sonum,itemlistbysonum(sohead.sonum) as itemlist ;
from sohead ;
where date=date() ;
into cursor tempcursor

This tells me that its not a buffering/caching problem with the computer inserting the records. Its a caching problem with the computer performing the SQL-Select. This problem is not limited to peer-to-peer networks either. I've seen it happen on computers that are using a real file server.

This problem is driving me insane. Any other ideas? Surely someone else out there has run into this before????