Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Observed behavior:
If I use USERID, works as expected
If I use NTName, does NOT work as expected
* Only change is commenting out the UserID line and uncommenting the NTName line*
Note that both userid and NTName are on the same line, and no other document settings were changed
On opening, see the OSName() shown as 'CUSTOM\pdbdeveloper', and the QVUser() = filled in (for USERID, shows entry, for NTNAME, shows nothing, but seems to verify that I'm using the 'Correct' NTName)
Key areas:
Directory;
Section Access;
NoConcatenate
Access:
Load
Upper(ACCESS) as ACCESS,
Upper(USERID) As USERID, // Works, but asks for double login
// UPPER(NTNAME) As NTNAME, // Gets login working, shows as NTName, but fails to do restriction
Upper(SECURITYLINK_TERRITORY) as SECURITYLINK_TERRITORY
FROM
[.\Excel Helpers\QuoteAccess.xls]
(biff, embedded labels, table is [Sheet1$])
;
Section Application;
Later on:
NoConcatenate
SecurityLinkTbl_Territory:
Load
Upper(SECURITYLINK_TERRITORY) as SECURITYLINK_TERRITORY,
(TerritoryCode) As [Territory Code]
FROM
[.\Excel Helpers\QuoteAccess.xls]
(biff, embedded labels, table is [Sheet2$])
;
Concatenate
SecurityLinkTbl_Territory:
Load Distinct
Upper('ALL') as SECURITYLINK_TERRITORY,
[Territory Code] As [Territory Code]
Resident Territory;
Spreadsheet contents (Sheet1):
ACCESS USERID NTNAME SECURITYLINK_TERRITORY
ADMIN ADMIN
USER PDBDeveloper CUSTOM\PDBDeveloper REGION_4
Sheet2:
SECURITYLINK_TERRITORY TerritoryCode
REGION_4 A37
REGION_4 A38
REGION_4 A39
Jim
I recently had a similar issues, with QV 11.2 SR5, that I could not get both USERID & NTNAME Section access working. To get it working I eliminated all the USERID elements as time was pressing.
This certainly is not a solution, but I will follow this thread with interest.
Best Regards, Bill
It's not even both, I'm just trying to switch, but seem to be hitting something
Tried a bunch of things on my own, but figure it's best to ask before continuing to blow too much time on it.