>>>This VFP 6 app has been running since 2001,
>>>Last week the client noticed that in the first line of a report (a grouped line) the numbers were doubled.
>>>Just the first line. All other lines were OK.
>>>A browse of the table showed that the data was correct.
>>>After futzing for a while, I reindexed the table and the report showed OK In the preview screen.
>>>That's the first time I've had to reindex a table in that app.
>>>This particular table is used to house monthly data and is zapped every month when the month is closed.
>>>I thought, "Wow 14 years and one blown index.. that's not shabby, is it?"
>>>Today, the same client called and said that the report was OK in the preview screen, but when she clicked the print button and printed the report, the first line was doubled again.
>>>I got the data here and was able to reproduce it.
>>>OK in the preview, doubled when printed.
>>>Strange.
>>>That's a first for me. I've seen many format differences but never saw a report have a different grouping result when printed.
>>>I reindexed the table again and packed it this time.
>>>Now the printed version is OK.
>>>Any ideas as to what might be going on?
>>
>>Bill, the fact that re-indexing fixes it (without any other changes or "fixes" being done) implies that this is indeed a database / index problem. Something is damaging the index. If this has been working on the user's machine without fail then I would begin by looking at what changed at the user. Is the hard disk OK (run chkdsk)? Is there AV running that could be interfering? Is this a network install or stand-alone? Is this a multi-user app - could other users accessing/updating the file be a cause? Has some new software been installed on the user machine? Run another (or 2) AV tool to double check the user machine is clean.
>
>In fact, this office of the client was recently the victim of a major hack and had to get all new workstations at that office.
>That would explain the blown index, but why the difference between the previewing and printing?

I dont know the answer but I am also not surprised as the rendering engine could be different between preview and actual printing, or possible some other difference between the two output options - I don't know for sure but not surprised.

The real question is; what causes the index (or data file) to be damaged or affected? Which goes back to my series of initial questions I guess... If this is a networked app and the workstations were changed then that implies new network cards, new hard disks, new servers?, new AV perhaps ... so lots of things now changed and perhaps causing some conflicts / corruptions ?