>>I'd expect that Windows does not place a lock during copying
>
>Actually, I'd be surprised if it didn't put a lock on a file. Otherwise, what happens if Windows tries to copy a block while another application is writing to that block?
Okay, that makes sense. My new hunch:
USE reacts well during copying of myTable.DBF, because it discovers that some other process is currently locking myTable.DBF. SET REPROCESS defines the behavior in that case. But when USE finds out that myTable.DBF is not locked, it will open it, only to find out a tiny bit later that myTable.FPT (or CDX too?) is locked. And then, instead of doing what it would have done if myTable.DBF was locked, it will generate the error 'Memo file is missing or invalid'.
What's your insight?
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.
