Hi Jeff. Many thanks for the reply
I can understand that, but why no issues before move to Windows 10
Also, 99% of time, no issues
I would have thought that, if there was an indexing issue, it would be there all the time, and not just on Windows 10 ?


>>Thanks Dorris for your reply
>>I would not have tough that it was a data issue, as most of the time everything works ok
>>If it was a data problem , that needed re-indexing, would it not give problems ALL the time, not just intermittently ?
>>
>>Regards,
>>Ger
>>
>>
>>
>>
>>>>One of our users has started getting this message (and others Unable to access ....) very intermittently , about 3 or 4 times a day on each pc
>>>>Only thing that has changed is move to New Pcs with windows 10
>>>>Is there any solution to this ?
>>>>
>>>>It is quite intermittent but no files are being corrupted, so looks like some sort of network issue
>>>>But Network guys saying network is running fine
>>>>
>>>>May thanks in advance
>>>>Gerard
>>>
>>>I ran into the same thing recently and ended up fixing it with a Verify Database to find the problem, fixed the problem, Packed the Database and reindexed all files. Seems (so far) to have fixed it.
>>>
>>>It's going to be a very short term problem since I'm converting to an SQL backend and should be finished shortly
>
>Gerard,
>
>It's very typical to get a total crash C00000005 or invalid seek offset if your indexes are corrupt. Re-index and it will be ok.