[WD55] How to repair a defective .MMO file ?

Hi,

I've got a set of WD55 data files from an old customer in order to transfer them to a WINDEV 20 program.

What I did before trying to read / insert the data by the new WD20 program:

- Re-Index with HIndex(..) with NdxDelete + NdxCompact - no error is shown!

In the old wd55 program, a certain datafile crashes when reading a record because of an error 7 (new = 70007) which is a hardware defect as they say. However, I can copy the files around, no problem with the files. There are much more than 8000 records in the file which stops me from looking at it with WDMAP. Obviously, only the .MMO file has been shortened by a harddisk error. It should be about 490.000 bytes in size, but in fact it is 475.000 bytes only. That wouldn't be a problem, this part of the file is not important to our customer, just remarks.

The data transfer is impossible because it stops with error 7 - hatdware fault:

Error at line 67 of Local Procedure Import_LSKOPF2 process.
HReadSeekFirst function called.
Error message returned by Hyper File 5:

Le mécanisme de sécurité d'HyperFile a été déclenché
L'incident détecté est vraisemblablement dû à un problème physique

Erreur: 7, Erreur de lecture
Fichier:MyLSKOPF, Enregistrement:79271

----- Technical Information -----

Project : BackPlusV2

WL call:
Process of 'Local Procedure Import_LSKOPF2' (ImportBPlusV1.PROCEDURE.Import_LSKOPF2), line 67, thread 0
'HReadSeekFirst' function, syntax 0

What happened?
Error message returned by Hyper File 5:

Le mécanisme de sécurité d'HyperFile a été déclenché
L'incident détecté est vraisemblablement dû à un problème physique

Erreur: 7, Erreur de lecture
Fichier:MyLSKOPF, Enregistrement:79271

Error code: 73500
Level: fatal error (EL_FATAL)
WD55 error code: 3500

Dump of the error of 'wd200hf.dll' module (20.0.115.2).
Identifier of detailed information (.err): 70508
Debugging information:
IEWDHF=8.38
Module=<WDHF>
Version=<20.0.115.2>
Fonction (7,12)
Additional Information:
EIT_LOGICALTABLENAME : <MyLSKOPF>
EIT_BASEMESSAGE : <
Le mécanisme de sécurité d'HyperFile a été déclenché
L'incident détecté est vraisemblablement dû à un problème physique

Erreur: 7, Erreur de lecture
Fichier:MyLSKOPF, Enregistrement:79271>
EIT_BASECODE : <7>
EIT_PILEWL :
Local Procedure Import_LSKOPF2 (ImportBPlusV1.PROCEDURE.Import_LSKOPF2), line 67
Click BUTTON (ImportBPlusV1.BUTTON), line 161
EIT_DATEHEURE : 09/04/2016 13:11:31

In fact, I cannot handle the error (or don't know how to do it). Is there a tool which repairs the hf55 .MMO file? Are there any tips for a repair procedure?

Hello Guenter

Could you alter the file in the analysis so that it doesn't have a memo and then it should open up ok Then you could copy a few 1000 records at a time into another file until you have as many records as can be recovered.

Regards
Al

Hi Al,

thank you for the idea! Using a Hex Editor I had a look into the .MMO file first and saw, that it mainly consisted of Hex 00. This "Error 7" appeared by pointing to a part of the MMO file which wasn't there anymore, presumably cut off by the NTFS file system during a crash, turning off of the computer etc. So, next I appended 40.000 x 00h to that MMO file and ho and belo, the import-program could read all of the file! Of course, those few remarks were missing, but everything's ok now. Thank you!