Bob & Colin: I checked the permissions and they are all propagated down through the subdirectories and files. Only server Administrators and the UniData group have control over everything under the "MyApp" shared directory, nothing else.
When I open a file I'm given a choice of how the file is opened: 1) Disk, 2) Ftp, and 3) UniObjects. I've been trying "Disk" but it appears I can't update these files because I've set them up so only server "administrators" and "UniData group" users can modify the files. From my workstation, I can view the files, just not change them. When I try access via UniObjects, I'm asked to provide my "server" user name and password (credentials). Upon entering these server credentials I can update the files. So, it appears when I connect to the "shared" directory on the server, using my workstation's Windows Explorer (or anywhere else for that matter), I'm using the "SYSTEM" windows user that I've explicitly removed from access to these directories. Therefore, when securing the directories, UniDebugger should only be used with UniObjects where the server's credentials can be entered and used...unless, of course, anyone else knows of a valid, secure, user/group that I can add to the list of authorized users of the "MyApp" directory to make the "Disk" option work. :-) Thanks. Bill > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > [EMAIL PROTECTED] > Sent: Tuesday, April 04, 2006 10:52 PM > To: [email protected] > Subject: RE: [U2] UD UniDebugger > > Bill; > > Which read/write type are you using when you open the file? > > If you use "disk" then it uses standard windows permissions > (i.e.. if you can > update the program in notepad you can update it in > UniDebugger). I have > mapped drive letters - but I wouldn't think it would be any different. > > I've never gone through the hassle of setting up ftp to work > on a windows host. > But I have used it on an Aix host. Standard ftp... > > Lastly is UniObjects. I've gotten it to work - just to make > sure I could. The > only benefit I saw was having the program actually locked at > the UniData > level - never found it worth the trouble. Using straight disk > is so much > easier. > > What type of permissions/security do you have on the share? > What if you use the full unc path? > What if you map a drive? > You're not doing something silly like logging in as someone who > isn't a member of the admin or UniData group? > Was the user recently added to the group? Sometimes it takes a > while to take effect. > > hth > Colin Alfke > Calgary Canada > > > > ________________________________ > > From: Bill Haskett > > Speaking of UniDebugger, how does one go about updating a > UniData file on > another server? > > I have UD 7.1 running on a Win 2K3 server. The permissions > on this server > allow Administrators complete control and the "UniData" group complete > control. The group of accounts I want access to is located > in "E:\MyApp\". > I've "shared" this directory as "MyApp" then in UniDebugger I > open the "BP" > file in "\\AsiDev\MyApp\Dta\BP" then select a program. When > I try to update > the program I get a message that I don't have permissions. > > What permissions should I give to "E:\MyApp" so that > UniDebugger can update > these programs? > > Any help would be appreciated. :-) > > Bill Haskett > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
