xBrowse intermittent "message not found: NIL:NLASTKEY error

Posts: 1096

Joined: Fri Oct 28, 2005 02:27 AM

xBrowse intermittent "message not found: NIL:NLASTKEY error
Posted: Wed May 11, 2016 08:09 AM

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

FWH 11.08/FWH 19.12

BCC5.82/BCC7.3

xHarbour/Harbour

nageswaragunupudi

Posts: 10733

Joined: Sun Nov 19, 2006 05:22 AM

Re: xBrowse intermittent "message not found: NIL:NLASTKEY error
Posted: Wed May 11, 2016 10:05 AM

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

Regards

G. N. Rao.

Hyderabad, India

hua

Posts: 1096

Joined: Fri Oct 28, 2005 02:27 AM

Re: xBrowse intermittent "message not found: NIL:NLASTKEY error
Posted: Thu May 12, 2016 02:33 AM

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

FWH 11.08/FWH 19.12

BCC5.82/BCC7.3

xHarbour/Harbour

nageswaragunupudi

Posts: 10733

Joined: Sun Nov 19, 2006 05:22 AM

Re: xBrowse intermittent "message not found: NIL:NLASTKEY error
Posted: Thu May 12, 2016 04:19 AM

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

Regards

G. N. Rao.

Hyderabad, India

hua

Posts: 1096

Joined: Fri Oct 28, 2005 02:27 AM

Re: xBrowse intermittent "message not found: NIL:NLASTKEY error
Posted: Thu May 12, 2016 04:41 AM

>>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

FWH 11.08/FWH 19.12

BCC5.82/BCC7.3

xHarbour/Harbour

nageswaragunupudi

Posts: 10733

Joined: Sun Nov 19, 2006 05:22 AM

Re: xBrowse intermittent "message not found: NIL:NLASTKEY error
Posted: Thu May 12, 2016 05:13 AM

>>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

Regards

G. N. Rao.

Hyderabad, India

FiveTech Support Forums

Continue the discussion