Skip to main content
Announcements
Introducing Qlik Answers: A plug-and-play, Generative AI powered RAG solution. READ ALL ABOUT IT!
cancel
Showing results for 
Search instead for 
Did you mean: 
racer25
Contributor III
Contributor III

Section Access in SQL (Not Working)

Hi All

Up until recently Section Access was maintained in an Excel file and worked file (albeit the limitations of Excels own security).

I decided it was time to move this file to our SQL server for security reasons which didn't go according to plan.

I copied and pasted the data from Excel into a SQL table matching field names from the Excel to the same SQL names (nothing changes). The Section Access approach I used was taking the NTNAME and no usernames or Passwords for End Users.

Section Access

USERIDPASSWORDSERIALACCESSUTBL_CONTROLNTNAME
**SERIAL NUMBERADMIN**
***ADMIN*domain\smith123

LOAD SCRIPT

Section Access ;

//LOAD [USERID],

//     [PASSWORD],

//     SERIAL,

//     [ACCESS],

//     UTBL_CONTROL,

//     NTNAME

//FROM

//..\..\XL Mapping Tables\Security.xlsx

//(ooxml, embedded labels, table is Master);

OLEDB CONNECT32 TO  SQL SERVER

LOAD USERID,

    PASSWORD,

    SERIAL,

    ACCESS,

    "UTBL_CONTROL",

    NTNAME;

SQL SELECT USERID,

    PASSWORD,

    SERIAL,

    ACCESS,

    "UTBL_CONTROL",

    NTNAME

FROM Qlikview.dbo."tbl_QV_Security_All_Access";

SQL Table

CREATE TABLE [dbo].[tbl_QV_Security_All_Access](

  [USERID] [nvarchar](255) NULL,

  [PASSWORD] [nvarchar](255) NULL,

  [SERIAL] [nvarchar](255) NULL,

  [ACCESS] [nvarchar](255) NULL,

  [UTBL_CONTROL] [nvarchar](255) NULL,

  [NTNAME] [nvarchar](255) NULL,

  [USERKEY] [nvarchar](255) NULL,

  [UserName] [nvarchar](255) NULL

) ON [PRIMARY]

I suspect my issue is something to do with the column types in SQL but really as I am NEW to SQL not sure at all and would appreciate some assistance as to why it would work in Excel and SQL.

Many thanks,


Rob

Section Application ;

1 Solution

Accepted Solutions
racer25
Contributor III
Contributor III
Author

I hope I figured it out with a bit more readying.

I changed the load to UPPER(Field) for each field name and it now works...

Thanks for your suggestion.

ROb

View solution in original post

2 Replies
Anonymous
Not applicable

Hi Rob,

Why don't you try to store the SQL data into a QVD and use that in SECTION ACCESS?

Regards

Jeba

racer25
Contributor III
Contributor III
Author

I hope I figured it out with a bit more readying.

I changed the load to UPPER(Field) for each field name and it now works...

Thanks for your suggestion.

ROb