I have code that checks to see who is logged on to the Win2K session. What I need is to be able to re-log that user as someone else at runtime. This is the code to check the current user:
Public Property Get CurrentUser() As String
Dim usr As String
Set wshnet = CreateObject(“wscript.network”)
usr = wshnet.UserName
CurrentUser = usr
End Property
I have an application published in a Citrix session. This VB6 app accesses an Access 2K2 database on another server. They want to restrict NDFS rights to the folder containing this Access DB to only one user. The idea is, in the Citrix session, I would like to re-log the user programmatically to another account that has access to see this folder.
. Our usual approach to this kind of thing is to actually track who is making changes to the database, so we don’t want to have a single userID. The reason is we want to identify users who are poorly trained, or who are accidentally or deliberatly misusing it. But the bottom line with any Access database is that the user must have full permissions on both the file and the folder it resides in. Otherwise Jet has no way of handling record locking, so it opens it exclusively. In general we set full permissions for everyone – so there isn’t a huge admin issue. What is the underlying reason for wanting to only have one userID have permissions?
