Hi
(sorry for the late answer, I've been offline for two days)
> ncafferkey wrote:
> Does the problem with the RAM-handler only arise when more than one program is using your library?
Yes that's true, even if more than one program accesses the same files in the ram-disk via my library, the ram-handler will not die, unless a lock-fault appears, i.e. one program still holds a recordlock, when another is trying to obtain a lock. (I've constructed this situation in my test-program, usually it is not a very frequent event).
But nevertheless this bug is annoying, it should not be. It is so easy to create a test for this condition, it should have been testet, found, and removed when the ram-handler was written BEFORE it was released.
Noster