xBrowse intermittent "message not found: NIL:NLASTKEY error

[hua]

I'm using FWH11.08. Intermittently the error below will appear. Where do I start looking to prevent this kind of error occuring?



TIA
--
hua

[nageswaragunupudi]

May I know
Did you sent oCol:lAutoSave to .T. ?
What is the data type of that column?

[hua]

Yes oCol:lAutoSave = .T.
I think the column's data type is character

[nageswaragunupudi]

1) Suggest leave oCol:lAutoSave as default .F.
2) Since you say this is an intermittent error, it can take a lot of time for us to figure out why and when this error could arise.
We'll try and if you can help us under what situation the error is coming that would be halpful

[hua]

>>1) Suggest leave oCol:lAutoSave as default .F.

If left as .f., then user can't immediately key-in? What's the alternative method?

>>2) Since you say this is an intermittent error, it can take a lot of time for us to figure out why and when this error could arise.
>>We'll try and if you can help us under what situation the error is coming that would be halpful

I understand. When I looked at the source I don't understand how the error could have happened because before it reach oEditGet:nLastkey it already passed oCol:oEditGet != nil
It's a long time bug that I couldn't duplicate how it occur

[nageswaragunupudi]

>>1) Suggest leave oCol:lAutoSave as default .F.

If left as .f., then user can't immediately key-in? What's the alternative method?

No
If lFastEdit is true, then the user can enter the get by pressing any key.

In fact lAutoSave is not very safe.
When lAutoSave is false ( default ), any value entered is saved only when the user expressly presses a key to terminate the Get. That is the user knows he intends to save the value.

If for some reason browse loses focus, the value is not saved.

When lAutoSave is .t., if for any reason browse loses focus, the partly entered value is saved without the user's express intention to save.

So, the default is safe. But as you know xBrowse provides for different tastes of different programmers.

I understand. When I looked at the source I don't understand how the error could have happened because before it reach oEditGet:nLastkey it already passed oCol:oEditGet != nil
It's a long time bug that I couldn't duplicate how it occur

Yes. You are right.
Same reason I am unable to quickly decide how to catch the situation