Does anybody have an example of how to identify and close open file locks. I have an application that's locking a db file on a Windows 2000 server. Users are inadvertently leaving themselves logged in over night preventing the file from being backed up.
I realize that there are risks in clearing these sessions from the server side, but I think the risk of missed backups at least warrants some testing (on something other than the live application db). I've thought of using "net file" and parsing the output to produce "net file" commands to close the sessions. Does anybody have a better idea? Thomas _______________________________________________ Perl-Win32-Admin mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
