Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
gbarrett
Partner - Contributor III
Partner - Contributor III

Qlik Sense: MS Access ODBC Load Error

Hello Community,

I am having an issue loading data into Qlik Sense from a MS Access table via ODBC connection. I am able to see the fields and data in the data preview of the connection, but when the script is generate and loaded, a SQL error appears. The following is my script that is generated without modification and the error message that comes with it. One thing I noticed that was off was the script did not generate  closing quotes or comma after the Credit Union field in the SQL Select statement. When I add that, the error still appears. The version of Qlik Sense is Qlik Sense 2.2.3 + Build: 3.7.release/ms15. Any help would be appreciated.

LIB CONNECT TO 'AccessDB_SIT (pscu_gbarrett)';

REM LOAD "Help Desk Agent",

    "Date   (mm/dd/yyyy)",

    "Time                (12 or 24 hour clock)",

    "Employee ID",

    "Agent Name",

    Location,

    "Call Type",

    "Credit Union                                                    ",

    Category,

    Reason,

    "Info in KB?",

    Notes;

SQL SELECT "Help Desk Agent",

    "Date   (mm/dd/yyyy)",

    "Time                (12 or 24 hour clock)",

    "Employee ID",

    "Agent Name",

    Location,

    "Call Type",

    "Credit Union                                                    ",

    Category,

    Reason,

    "Info in KB?",

    Notes

FROM "C:\QlikData\Call Center\Help Desk Tracker.accdb".Tracker;

The following error occurred:

SQL##f - SqlState: 07001, ErrorCode: 4294964286, ErrorMsg: [Microsoft][ODBC Microsoft Access Driver] Too few parameters. Expected 2.

3 Replies
awhitfield
Partner - Champion
Partner - Champion

Hi George,

check out the following thread:

https://qlikcommunity.qliktech.com/thread/150355

Andy

gbarrett
Partner - Contributor III
Partner - Contributor III
Author

I figured out what was wrong but I don't know why it is wrong. The question mark in the "Info in KB?" field was causing the issue. Once the question mark was removed from the field name in the Access table, the script worked. Can anyone elaborate on why that happened and if other special characters can do this as well? Thank you.

Anonymous
Not applicable

It's probably because it is an Access wildcard like '*'