NO_CARRIER
asked on
Users currently sharing an executable?
My application is on a shared network drive. Anyone in the department can open / access it.
However, sometimes in the evenings when I want to put a new build on the network there is a sharing violation. Some users lock their computer with the application open.
I'd like to be able to track which users are currently using the application. Perhaps a text file of some type with a time-stamp, and is updated every 5 minutes or so... (timer), if it's not updated it times out and removes the user from the list?
Is there another method to do this? I'd just like to track which users have it open.. so if necessary I can unlock / reboot their systems.
Thanks,
NC
However, sometimes in the evenings when I want to put a new build on the network there is a sharing violation. Some users lock their computer with the application open.
I'd like to be able to track which users are currently using the application. Perhaps a text file of some type with a time-stamp, and is updated every 5 minutes or so... (timer), if it's not updated it times out and removes the user from the list?
Is there another method to do this? I'd just like to track which users have it open.. so if necessary I can unlock / reboot their systems.
Thanks,
NC
Mikal613
If there is a database attached to it you can have your program looking for a field (every minute) yes/no if yes then shutdown and when you wanna update then just update that field
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
yes, the exe is currently hooked up to a database... (does not connect at runtime though.)
Forcing to shut down is an option, but it could become annoying to some of the rep's here.
Would there be a problem of simply adding their lanID to a text file when the open the application, and remove their name on unload?
Forcing to shut down is an option, but it could become annoying to some of the rep's here.
Would there be a problem of simply adding their lanID to a text file when the open the application, and remove their name on unload?
Adding the LAN ID to a text file when the app starts and removing it when it unloads presumes that the app will always shut down gracefuly. What happens when it doesn't? There are any number of situations that could bypass a graceful shut down. Things like a the PC losing power, an OS crash, an employee terminating the app via task manager, etc. Any time the app didn't go through a normal shut down, then that LAN ID would still be there in the text file leaving you to believe that the app was still running on some PC. How would you handle startup if for some reason the app couldn't write to the file holding the LAN IDs? That's probably less of an issue than the app not shutting down properly, but it is still a possibility.
I'd think the second option I discussed would be the best. Add a timer control and check for a given file or an entry in a file periodically (i.e. some triggering option). If the app sees the trigger, then it pops a nice notice up on screen telling the user that it's going to shut down in a certain amount of time, then goes through an orderly shutdown. The code for this is very simple. Here's an example:
Dim objFSO as FileSystemObject
Private Sub Timer1_Timer()
If objFSO.FileExists("C:\Kill
'Shutdown code goes here.
End
End If
End Sub
Private Sub Form_Load()
Set objFSO = New FileSystemObject
Timer1.Interval = 60000 'Check for the file once a minute
End Sub
I'd think the second option I discussed would be the best. Add a timer control and check for a given file or an entry in a file periodically (i.e. some triggering option). If the app sees the trigger, then it pops a nice notice up on screen telling the user that it's going to shut down in a certain amount of time, then goes through an orderly shutdown. The code for this is very simple. Here's an example:
Dim objFSO as FileSystemObject
Private Sub Timer1_Timer()
If objFSO.FileExists("C:\Kill
'Shutdown code goes here.
End
End If
End Sub
Private Sub Form_Load()
Set objFSO = New FileSystemObject
Timer1.Interval = 60000 'Check for the file once a minute
End Sub