Under v9 (Sorry - don't have v8 Documentation!) there is the -vss switch for the clients.
Danger - This means that you can only have ONE instance of Progress client running on your PC, which means that if you have 2 Progress applications they cannot work together.
The only alternative is to take out a share lock (be VERY careful with this) on some user control record when they log in. This way, when they die the share lock is released and they log back in. If they try to log in a second time they will not be able to acquire the share lock and this can be trapped.
You can try updating a record to say that they are logged in, but Windows notorious stability will mean that you will need a routine for resetting these periodically.
The share-lock solution actually works something like this.
do for <user-lock-record-table>:
do transaction:
/* Must find it exclusive otherwise find will succeed */
find <user-lock-record-table>
exclusive
where login = <login id>
no-wait no-error.
end.
if not avail <user-lock-record-table>
then do:
message "Your user id doesn't exist or is already in use" view-as alert-box info.
quit.
end.
run <normal startup procedure>
end.
The danger with this is that your record scope on the <user-lock-record-table> is necessarily the entire session and can cause issues with poor programming technique.
