>Hilmar,
>
>I'm aware of both proposed solutions, and have used both. I was hoping for a VFP coding trick to preclude these time consuming work-arounds.
>
>Thanks regardless.
>
>F.Z.
I don't think so, because if ANOTHER program has a file in use (really, or only apparently, because of an OS-problem), it is not up to VFP to say that the file is NOT in use by another program. To keep things orderly and safe, the OS has to take control that a locked file remains locked - until the program that locks the file unlocks it.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)