Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I have a .qvw file with "section access" in the script:
SECTION Access;
LOAD [ACCESS],
NTNAME
FROM
(biff, embedded labels, table is SICURA$);
SECTION Application;
...
The excel file is here attached
It seems all pretty simple, BUT a user can't see the .qvw file in the access point (INFOSYN\KPLONER)
Instead, I can see it, with my profile (INFOSYN\MMIORANDI)
I really cannot understand why it behaves this way
Any idea about it?
Indeed, it was some kind of windows security problem
A shared folder was created, the one with the qlikview file inside
I don't know why but the users who hand't permission to access the shared folder also couldn't see the qlikview files in the access point
Maybe it's not the only reason - but you must use upper() in section acees except in load inline:
LOAD
upper([ACCESS]) as ACCESS,
upper(NTNAME) as NTNAME
FROM...
hi michael,
unfortunately this change hasn't solved the problem
the weird thing is that one user can see the file, but other users cannot
what could it be?
"Can't see the file" is not the same as "can't open the file". It has nothing to do with Section Access, I think, - you can verify it by remoiving Section Access.
It is probably a restriction to the file itself on the Windows file security level.
The user can't see the file in the access point
But as you said it is not a section access problem, because i removed it and that user still can't see the file
I'll try to contact the system admin now
Thanks
Check the username & password, URL, IE settings.
Try to check on different system i.e, ask the user to check the access point on your system.
Hope it helps.
Hi mmiorandi.
The SECTION ACCESS statements has nothing whatsoever to do with which applications users see on the AccessPoint. This is instead controlled by the Windows File Security. Right click the file > Properties > Security. There you can explicitly define which users/groups who can see the file on the AccessPoint.
SECTION ACCESS is applied after a file is opened.
Kind regards
BI Consultant
Indeed, it was some kind of windows security problem
A shared folder was created, the one with the qlikview file inside
I don't know why but the users who hand't permission to access the shared folder also couldn't see the qlikview files in the access point