Unable to use Variables with SQL Statements inputting to Access

(1) Share

Report

Posted on by Woody Chandler

Hello. I am attempting to place variables gotten from my flow onto an Access Database. Whilst doing this, I have been unable to actually add any. No iteration of signs around the variables gets them to work, and I have looked for a while. I may have just been overlooking something or mistyped, but I need help now.

My current code for it is below, but as I have said- it does not work

INSERT INTO ImageBase (Forename)

VALUES

(%'FirstName'%)

Following advice I have found, I have put ' punctuation marks around the variable name, leading to the name of the variable being written into the table- rather than the actual variable insides. Using % signs around it returns a Syntax Error. Any help will be greatly appreciated.

I do have PowerFX enabled for my flow, and below is a screenshot of the actions I'm using to attempt this process.

Categories:

Process Advisor

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

Sam_Fawzi 590 Super User 2025 Season 2 on at

Like (0)

Report
Unable to use Variables with SQL Statements inputting to Access

Hey @Woody Chandler

Try using parameters. Do not put % or quotes around the variable name. In Access/ODBC the placeholder is ?.

INSERT INTO ImageBase (Forename) VALUES (?);

Parameters (in the action)

Type: String

Value: @{variables('FirstName')} or the dynamic content from your flow

The connector will pass the value and handle quoting. Putting 'FirstName' inserts the literal text FirstName. % is a LIKE wildcard, not a variable marker.

If you must build the SQL string yourself (not recommended), escape quotes:

INSERT INTO ImageBase (Forename) VALUES ('@{replace(variables('FirstName'), '''', '''''')}');

Checks:

ImageBase.Forename is Text type.

No trailing semicolons or extra lines in the action.

For multiple fields:

INSERT INTO ImageBase (Forename, Surname) VALUES (?, ?);

Add two parameters in order.

Was this reply helpful? Yes No