Fabio,

>Then the buffering is unimportant, because if the data is on the buffer of the 1st user,
>never query can show them to the second one.

You confuse what I'm talking about.

In a table/view with table buffering enabled a SQL select will not see the pending changes in the buffered data, a SCAN loop does see the change. Once you issue a TableUpdate() a SQL select will see the changes.

>Why the second user can see the new data inserted by the 1st ?
>Because the query scan the table without use the cdx index.

The CDX has nothing to do with this Fabio. As I posted in my other reply to you this morning the data is available in the DBF and the CDX at the same time.

>
>however, once the document number is retrieved by this search screen to the transaction screen, the new record cannot be retrived by the transaction screen of the second user
>
>
>Why the second user can not load the new data inserted by the 1st ?

Yau, never has posted back any information on the buffering model he is using. If the 1st user has buffering enabled and a TableUpdate() has not yet been issued, then the data doesn't exist to any other user. Once TableUpdate() occurs the data is available to other users.

>This because this use the cdx index,
>but the new record inserted by the 1st user it is remained in the VFP buffer of the index
>(it is not flushed into the cache of the OS).
>My first message show this fact; in fact, the ADIR() read the data by the
>OS cache !

This is a false assumption on your part.

>This is the reason for which, in the other message, I have written to you that what you have written is not correct.

It really doesn't do anyone any good for you to post this sort of message:


<snip>

My comment: all wrong.

Fabio

Without any explanation or evidence to show what you think was wrong in my post.