Page 3 of 3
Re: Question about XBROWSE
Posted: Fri Oct 01, 2010 7:47 pm
by Enrico Maria Giordano
Gale FORd wrote:Yes, it is the controlling index. It must have something to do with the nature of a temporary index.
So try without TEMPORARY clause and let me know.
EMG
Re: Question about XBROWSE
Posted: Wed Oct 06, 2010 3:50 pm
by Randal
Gale:
Interesting thread, thanks for your comments and testing.
Do you think it's safe to use cmxShared(.f.) to load records into a browse or array and then call cmxShared(.t.) after they are loaded?
Using cmxShared(.f.) doesn't appear to effect the ability to lock and update a record in a multi-user environment.
What kind of problems might one encounter doing this?
Thanks,
Randal
Re: Question about XBROWSE
Posted: Wed Oct 06, 2010 5:52 pm
by Gale FORd
My understanding is that with the dirty read turned on ( cmxShared(.f.) ) then you might skip to an invalid record or a seek would show found() but the data does not match.
The speed difference on a network drive is really tempting but I am very careful with this option.
I have tried to put history data in another database so I could use this option. Current and constant changing records are another story.