VB6 SHGetFolderPath for network shares
Our VB6 app uses SHGetFolderPath to get CSIDL_PERSONAL for the users documents... to then store their data files there.
We have a company in a corporate environment that has mapped Documents in Windows 7 to:
\\capfs01\usersname$
which is a network share....
When we try to read or write that path it does not work....
We are using FileSystemObject .... should that automatically handle these weird network share paths in Windows 7 and Windows 2008?
We have a company in a corporate environment that has mapped Documents in Windows 7 to:
\\capfs01\usersname$
which is a network share....
When we try to read or write that path it does not work....
We are using FileSystemObject .... should that automatically handle these weird network share paths in Windows 7 and Windows 2008?
ASKER
Yes it does to me... but I did not set up these shares... just a customer I'm talking to over the phone....
They claim though that there is no problem with any other apps.... and he claims that they have "full permissions" on the share.... so maybe they do on the share but not higher up the chain?
It thought you could hone in on permissions at a folder level even if you have zero access rights to anything above it????
They claim though that there is no problem with any other apps.... and he claims that they have "full permissions" on the share.... so maybe they do on the share but not higher up the chain?
It thought you could hone in on permissions at a folder level even if you have zero access rights to anything above it????
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I cannot confirm whether either of this are the solution or help.... client could not get it to work... we still don't know the solution.... I do believe he was going to delve deeper into this permissions issue though....
Not sure what to do at this point. I can gladly assign some split points but then I still don't have an answer to the issue.
Not sure what to do at this point. I can gladly assign some split points but then I still don't have an answer to the issue.
Please do.
ASKER
EE is supposed to help us find answers... deleting questions does not help.
I can understand if someone solves the problem and the receiver does not bother to award the points... that's unfair and should be forced...
But when a question needs to stay in db in case someone else knows the answer... forcing a delete is not the solution... especially when I am paying you monthly for my EE account.
I can understand if someone solves the problem and the receiver does not bother to award the points... that's unfair and should be forced...
But when a question needs to stay in db in case someone else knows the answer... forcing a delete is not the solution... especially when I am paying you monthly for my EE account.
your NTFS root has DOMAIN_USERS to READ ONLY, and below that a few levels you have a share called \\server\share$, you're probably focusing all attention on the permissions and security for "share$" and not the parent folder security itself. The reason this is important is because of how your software/program/app is referencing the final end-point "share$"
does that make sense?