Aah, but it's not in our hands. Inspired by what you suggested, it is my hunch that it is caused either by copying, done by someone or by some process, or it is the virusscanner. And the memofile is not corrupted at all. This I can affirm.
I understand from your answer that you have no special handling in your exception handler.
I think I'll gonna handle the specific errornumber by RETRYing a number of times.
Thanks for the feedback.
>I didn't encounter such error on regular basis and when I did it was memo corruption. There's no point to continue in such case until table is repaired.
>The problem lies outside of VFP. Why copy is performed outside VFP in the first place? If you do it using COPY TO command, you wouldn't have the problem.
>
>>Okay, one final question to you and others: Is this kind of exception explicitly handled by your exception handler? If so, what type of handling can be advised here?
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.