A further point to Larry's remark about someone closing the session on the remote computer. Since Terminal Services is running all the processes on the server, when one closes the Remote Desktop Program on the remote computer without logging off the server (such as clicking the X in the upper right hand corner) the server still sees the session as running normally. This function is intentional and is very handy at times. This also happens if a user loses their internet connection if running over the net. They can reconnect and continue with the same screen they were on before and not lose any data etc.
However, if a user closes the Remote Window and leave the session running on the server, you can "kill" the session from the server, but that may not always be advisable, depending on where the user left their program. I normally log into the Terminal Server as a user with admin privilege, bring up the Terminal Services Manager and CONNECT to the open session. This will bring up the screen just as the user left it. You can then exit any software that was left open and properly close down all files. Killing the session may cause some half completed transactions or other problems.
Other than the above, I have never had any Rbase files left locked or open using Terminal Services.
-------------- Original message --------------
> > My problem with one user in particular is the "phantom user", which
> > prevented them from reloading their data base in single user mode and I
> > have maintained is a result of one or more users exiting RBase improperly.
>
> It sounds more like someone exiting Terminal Server Client improperly -- just
> disconnecting the seesion without closing down R:Base at all. It's easy to do,
> and it's actually legimate if you are just temporarily dropping the session and
> want to resume it later.
>
> > Emmitt pointed out that if the data base is "stuck" open, you can normally
> > go to My Computer, Manage, Shared Folders, and usually close the open data
> > base. I haven't seen this, but I've been told that the data base can be
> > "locked open" and then the server must be restarted.
>
> Emmitt's right. You can always "kill" the connections to the active database
> this way, no server restart required. Then, the next use in to R:Base should
> "detect" that they are the only user and clear all the locks inside the
> database.
> --
> Larry
>
