Choosefile initial directory restrictions (OpenInsight 32-Bit)
At 10 SEP 2007 02:55:22PM Richard Hunt wrote:
Is there a way to use the "CHOOSEFILE" utility and also restrict the user to only see and access the initial folder and it's subfolders.
An example…
VALUE=initial directory, or VALUE=c:\temp\'
I do not want the user to access the 'C:' or even view it's contents. I just want the user to be able to "save as" within the 'c:\temp\' folder or its subfolders. Is that possible?
At 12 SEP 2007 12:20PM dsig@sigafoos.org wrote:
I don't believe there is.
You could write your own little routine using setinitdiroptions, initdir and dirlist. Then you control where the can be.
Might be a good routine to share
At 12 SEP 2007 12:51PM Richard Hunt wrote:
After all the reading I did, I do agree with you. Doh!!! I just wonder how "terminal server" users get around this.
At 12 SEP 2007 08:37PM Karen Oland wrote:
In terminal server, you can control whether or not users see their local directories (we've had to turn it on here and there, so managers can save to local drives to play w/ data in excel offline, but leave it off for most).
More annoying is that choosedir ignores the starting directory location and we had to drop using it at all (or everyone would pick the Oinsight directory to save their exports or would keep calling asking where their import files were supposed to be located).
At 13 SEP 2007 11:19AM Warren Auyong wrote:
I think the trick is that unless the startup drive on TS server is mapped to greater then E: you have to use the UNC \\TS$Client (or something like that) to access the local drive on the workstation where the TS client is running. The same with Citrix.
If the initial directory doesn't exist, choosefile/choosedir ignores the setting and defaults to whatever.
The other trick is to determine if a user is running local or through TS/Citrix. One way is to check the environment variables.
See the threads on determining special folders like "My Documents" for details.
At 13 SEP 2007 12:06PM Richard Hunt wrote:
Yea… I kinda agree and I believe that Microsoft has designed this routine with a bad security issue.
I have created my own procedure so as to restrict users to their own workstation (or actually the selected folder and its subfolders). Since I am basically using this routine to allow users to save reports and PDF's, they can save these files on their workstation. I do not want them on the server, and I do not want users to browse the folders on the server.