records disappear [solved]

[lucasdebeltran]

Dear friends of the forum,

A customer reported me that some records in a .dbf just disappear.

Occupies 10 MB and has over 11,500 articles.

Works in single user, no network, with Windows 8.

The thing is, I have no idea why it happens. I check the DBF, I can open it and Idon´t get errors like corruption, etc, but the records are gone. I try to use a recall but they don´t appear.

Customer has´t done a PACK.

Has anyone experienced a problem like this?. It is very rare.

Thank you. Best regards

[MarcoBoschi]

Who uses this table?

[lucasdebeltran]

Just only one user in a sigle PC. No network used.

Thanks.

[Otto]

How do you know records where there.
Did you commit the input.
Windows restore point?
Best regards,
Otto

[fraxzi]

Hi!

This can happen if table header was corrupted. It is very important that all table must be closed when user end the program.
This was an experienced when DOS based app was closed by user by clicking the close button of DOS box and not the 'quit' button of the actual app.. (so upgraded to FWH)


My two cents.

[TimStone]

I had that happen last week. A customer had an invoice open and went to print it. He was on a workstation. ( There are six files, plus 4 fpt and 6 cdx files open ). When he sent it to the printer, the system locked up. He went back in and the main invoice record ( in one file ) wasn't there. I checked ... it simply wasn't there The data in the other five files that tied to this record in the primary were all in place.

I've had people report this but thousands of these records are added each week at various sites, and I may get one record per every two months that just never gets saved. Its way to difficult to track or reproduce, and it is not even consistent to a particular site.

Tim

[lucasdebeltran]

Thank you for the feedback.

It seems that is the Microsoft antivirus:
http://answers.microsoft.com/en-us/prot ... d96ee73f17

I am going to unisntall it and check what happens.

[Otto]

Lucas,
I repost my questions:

How do you know records where there.
Did you commit the input.
Windows restore Point?
Are these records at the end of the database are these old entries.

Sure you check the database with no index opened.


Best regards,
Otto

[lucasdebeltran]

Otto,

>>How do you know records where there.
In previous backups they were.

>>Did you commit the input.
There is no network mode. Besides, before exiting I do:

Code: Select all | Expand

  DbCommitAll()      // Guardamos datos
   SysRefresh()
   DbCloseAll()
   ResAllFree()       // Liberamos recursos

   //CheckRes()

   QUIT
 

>>Windows restore Point?
No.


>>Are these records at the end of the database are these old entries.
Old entries.


>>Sure you check the database with no index opened
Of course, with CDBF Viewer

[Otto]

Lucas,
do you use CDX.
This index has autoopen.
I am sure you know it.

Best regards,
Otto

[Otto]

Lucas,
is this WINDOWS 8 release version.

The preview Version since some days shuts down without warning every hour.
Best regards,
Otto

[Enrico Maria Giordano]

Are these records at the end of the database are these old entries.

Old entries.

A record that is not the last one simply cannot disappear without a PACK.

EMG

[Maurizio]

Like Enrico wrote :
A record that is not the last one simply cannot disappear without a PACK.

Have you checked what happens when you compare the same record number between the file copy and the actual file ?
If you use DATABASE class with aBuffer , It happens sometime that the record pointer changes ( for example in a browse )
and executes an update on a different record . Checks whether there is an overlap of records and not a loss .

Maurizio

[Jeff Barnes]

A record that is not the last one simply cannot disappear without a PACK.

I would disagree with the above statement....

I have a app that was written years ago used for generating service reports.

Every now and then (very rare indeed) I will notice that a record has gone missing.
I know the record did exist at one point since I have a paper printout that shows the record existed.
Since the missing records are from past years I also know they are not the last record in the database.
Also, since these service reports are to track repairs done on medical equipment I have not included a PACK function as I do not want the end user to be able to permanently remove a record (in fact they cannot even delete a record ... only I have that ability).

I have verified that it is not an index issue (opened the database without any index via a third party program).

It would seem that there is a little gremlin running around stealing our data every now and then

[Enrico Maria Giordano]

A record that is not the last one simply cannot disappear without a PACK.

I would disagree with the above statement....

To physically delete a record that is not the last one you would have to copy all the records in a new table excluding that one. Or copy all fields from the next record and so on to the end of table. There are no other ways, as far as I know.

EMG