Hi Jim,

I agree with you on that point. It's much better to stabilize things up before addind new features that will probably have to be fixed as well.

For the experiment I made, I have set REFRESH to 2.

Claude


>Claude,
>
>This is definitely one of the many areas where the VFP documentation, especially the Help, nedds serious beefing-up!
>
>They nedd only TELL US what they have designed it to do - nothing more, nothing less.
>
>As it stands now, we all have to guess! You seem to be satisified with what you have observed, BUT HOW would you feel if Erik's experience was actually the correct one and, lets say, your observation occurred simply because you had set REFRESH set too high and didn't wait long enough???
>
>This is *NO* way to document a system, nor can we be expected to develop production-scale and quality applications with MAJOR unknowns like this!
>
>We would be far better off having a DOCUMENTED and **FIXED** system than we would be having yet another version with yet more bugs and same quality documentation!
>
>Someone has started a "lets get what we have fixed before we get NEW functionality" movement over in the MS newsgroup for VFP. Sure hope he comes here (as has been suggested to him [Carlos, are you here????] and starts the same thing!
>
>Cheers (yea!)
>Jim N
>
>>>>>I am wondering,
>>>>>if the application accesses a database on a network drive, the form has buffer mode set to "optimistic table buffering", are new records appended buffered on the network drive or in a temporary file on the workstation ??
>>>>>
>>>>>Claude
>>>>
>>>>Hi Claude,
>>>>
>>>>I can't speak authoritatively on this, but I would expect the bufferred data resides in the location of the VFP TEMPWORK, SORTWORK, etc. directories.
>>>>
>>>>Bill
>>>
>>>I have tested this by watching a browse window (REFRESH SET TO 1) while another user appends a record in a form with table buffering. I _was_ able to see the new record before tableupdate was issued. This sort of cloudied things up for me a bit as far as table buffering goes. I would like to know the gory details also.
>>
>>
>>That worked ok for me. The browse view didn't show me the new records I was adding in my form until I clicked my save button which does the tableupdate.
>>
>>Claude