My users run access run-time from a citrix terminal server. I have code that collects the windows user name and PC name everytime someone logs in or logs out. (I'm using Dev Ashish's functions fosUsername and fosMachineName.) This is a great help in tracking down problems when they occur, helps me kick people out of the app when I need to do maintenance, etc, etc.
Problem is, when running from a terminal server, the PC name that gets returned is just the name of the server; what I need is the name of the PC or thin-client that the user is on, so that I know the actual physical location to go to.
Anybody know how to get this?
FYI, more background: This is in a manufacturing environment where there are many users per PC. We use a "shared" login name, as it's just not feasible to have people logging in and out every 5 minutes. What I've done in the past is to require a different shared login name for each PC. That way, I could tell , just by using fosUserName , which PC was in use. However, our IT department says the new rule is "no more shared login names", although they're willing to let us keep using the couple that we've been using for years.
I'm in the process of expanding the application to a bunch more PC's, but when I asked IT to creat more shared logins they said no. If necessary I will go to battle with them but hoping I don't have to.
Thanks for any ideas.
Problem is, when running from a terminal server, the PC name that gets returned is just the name of the server; what I need is the name of the PC or thin-client that the user is on, so that I know the actual physical location to go to.
Anybody know how to get this?
FYI, more background: This is in a manufacturing environment where there are many users per PC. We use a "shared" login name, as it's just not feasible to have people logging in and out every 5 minutes. What I've done in the past is to require a different shared login name for each PC. That way, I could tell , just by using fosUserName , which PC was in use. However, our IT department says the new rule is "no more shared login names", although they're willing to let us keep using the couple that we've been using for years.
I'm in the process of expanding the application to a bunch more PC's, but when I asked IT to creat more shared logins they said no. If necessary I will go to battle with them but hoping I don't have to.
Thanks for any ideas.
