Section Access - SQL vs. Excel - Some users can't access.

[racer25]

Hi All,

I am having an issue with Section Access for one or two users.

I managed access through a SQL table and for all but one or two users this works fine. Historically Excel was the choice and this was 100% no issue.

The Section Access table is below along with the script.

Section Access ;


OLEDB CONNECT32 TO  "THE DATABASE";


SECURITY:
LOAD upper(USERID) as USERID,
    upper(PASSWORD) as PASSWORD,
    upper(SERIAL) as SERIAL,
    upper(ACCESS) as ACCESS,
    upper(NTNAME) as NTNAME,
    upper(SA_USER_LINK) as SA_USER_LINK
where NTNAME  <> 'AONNET\adavis18';

SQL SELECT USERID,
    PASSWORD,
    SERIAL,
    ACCESS,
    "UTBL_CONTROL",
    NTNAME,
    SA_USER_LINK
FROM Qlikview.dbo."tbl_QV_Security_Broker_Access"
;


SECURITY:
LOAD USERID, 
     PASSWORD, 
     SERIAL, 
     ACCESS, 
     NTNAME, 
     SA_USER_LINK
FROM
[..\..\XL Mapping Tables\Security_BrokerDash.xlsx]
(ooxml, embedded labels, table is Master);


Section Application;

For adavis18 I have had to filter the user from the SQL load and then concatenate in from an Excel file.

USERID	PASSWORD	SERIAL	ACCESS	NTNAME	SA_USER_LINK
*	*	*	ADMIN	AONNET\adavis18	DAVISA01

This all works ! But I shouldn't have to do it this way as it works for virtually all users.

Today the colleague nbanks2 advises he can't access and it appears to be the same issue. Maybe its absolutely pure coincidence that they are next to each other on the list ?

Below is the field structure in the SQL database if it offers pointers.

	[UniqueKey] [nchar](10) NOT NULL,
	[USERID] [nvarchar](max) NULL,
	[PASSWORD] [nvarchar](max) NULL,
	[SERIAL] [nvarchar](max) NULL,
	[ACCESS] [nvarchar](max) NULL,
	[UTBL_CONTROL] [nvarchar](max) NULL,
	[NTNAME] [nvarchar](max) NULL,
	[USERKEY] [nvarchar](max) NULL,
	[UserName] [nvarchar](max) NULL,
	[SA_USER_LINK] [nvarchar](max) NULL,

Is there anything I can do to resolve this without ending up with some people in an Excel table. Is there anything else I can supply to help with this conundrum?

Thanks,

Rob