Hi Cindy,
In a message to Roger Nelson you wrote:

 CH> Nod.. Well I remembered that semaphor file and now know what it is and
 CH> what to do about it when it doesn't close. Good thing we can get into
 CH> the program via windows explorer. Boy. YOu know that is a flaw isn't
 CH> it? If you make a program so it won't open if it wasn't closed
 CH> properly because it think s it's still open.. and there's no other way
 CH> to get at it inside to delete the file that gets formed when it's
 CH> opened correctly...(and deletes itself when closed properly- It's
 CH> toast.

actually it is not a bug... it is a design feature... the main intent is to
prevent the application from being opened more than once... seems to me
that it works quite well, actually ;)

now, when the machine crashes, there's no way the application can remove
the semaphore file... this is why one of the first startup routines my
servers perform during the boot process is to remove all semaphore files,
if they exist, during the start up, before the applications are started up
;)

Bye bye!
  mark

 * SeM. 2.26  * I have never been beat by a barrier between me and my intended