FWH-XHARBOUR : FAULT IN PROGRAM

[demont frank]

Hello,

This week i got a serious problem in a fwh-xharbour program : it seems to me that the program makes a fault in the current session from the program.

From a xbrowse is a new record appended (routine is used for years) , edited and saved. The user print it and has only some fields on the print , other empty's.

Returning to the browse , the record IS NOT VISIBLE (append to the list) , so he tries again.

Same result. Supposing the program has a error , he start an older version from the program . Now he sees the appended records and has to delete them.

On this way i could examine the content from the saved records : it was normal , the records were saved correctly.

I suppose that when he restartded the current program , also then all would be normal.

I am convinced that the session from the program he was working with , made some inexplicable errors.

Am i the only one who has encounterd such behaviour ? Or must i suppose that i am missing something ?

With other words : can a program make some inexplicable faults in a current session going away in the next sessions ?

Frank

[nageswaragunupudi]

I understand the problem. One probable reason could be that oBrw:Refresh() is not used after saving the newly appended record.

[demont frank]

I understand the problem. One probable reason could be that oBrw:Refresh() is not used after saving the newly appended record.

No , if so the error should occur also at other moments . Refresh is present in the code

There is something wrong at the moment the record is printed , some fields seems to be empty , i do not found that in the record

I must say that i described the problem very short : records seems to be written as expected , but results (printing , xbrowse) are unexpected

Frank

[Antonio Linares]

Frank,

This seems quite obvious, but is he using an updated anti virus ?

Is his Windows stable and with all updates installed from Microsoft ?

What Windows version is it ? Are other applications working fine ?

[demont frank]

Frank,

This seems quite obvious, but is he using an updated anti virus ?

Is his Windows stable and with all updates installed from Microsoft ?

What Windows version is it ? Are other applications working fine ?

Antonio,

First : the reported error was the only one i had . I have no other error's from that kind

So far as i know , i have to answer yes on all questions

Frank

[Antonio Linares]

Frank,

What Windows version is it ?

[James Bott]

A corrupted index could cause this kind of behavior.

James

[demont frank]

A corrupted index could cause this kind of behavior.

James

james

yes , i know , i spended hours .

But , if so , only the current session has the problem. So as reported , an older version from the program , or probably a restart from the program has not the problem. The indices are not rebuild when the program starts again.

Frank

[Antonio Linares]

Frank,

Could you try to isolate that browse and make it into a small sample ? thanks

[demont frank]

Frank,

Could you try to isolate that browse and make it into a small sample ? thanks

Antonio ,

No , it is to complicated , i try to explain :

A record is created , it should update the x-browse.

This record creates 5 (in this case) child records . After saving the input record the user tries to print it.

To print , the program search for the first child record and makes then a search for the parent record.

The parent record is found , the print shows a text that is only present in this record from the hole database , record pointer is absolutely right. So i suppose that the linking field is correct in both databases

Only , the child records seems to be empty. But , when i look in the database this records seems to be normal , all data are as expected. Only explanation could be that wrong records are used in the child database , but i have no explanation for that.

After that the parent record is not visible in the xbrowse

The error could not be duplicated , at least on mine computer.

Frank

[James Bott]

Frank,

>But , if so , only the current session has the problem. So as reported , an older version from the program , or probably a restart from the program has not the problem. The indices are not rebuild when the program starts again.

If you are running different versions of the same program without reindexing this could be the problem. The index could be different due to changes in (x)Harbour. I suggest running the new version and reindexing first to see if the problem goes away.

James

[fraxzi]

Hello,

I experienced 'faults' usually if the apps.exe is using some kinda compression. If compressed, try not to compress.


Regards,
Fraxzi

[demont frank]

Hello,

I experienced 'faults' usually if the apps.exe is using some kinda compression. If compressed, try not to compress.


Regards,
Fraxzi

Thanks , i will try it . I was using upx

Frank