Encoding Escape Characters In SQL Statements Executed Through PowerShell

Hello,

I am attempting to execute a an SQL query through PowerShell against an MS Access database.  My query works 99% of the time, but occasionally a localized string will cause an error beacuse it contains a single quote (') somewhere within the localized string.  You can look at the following example to get a better idea of what I am talking about:

SELECT TermNo, File, Context
FROM ExceptionFC
WHERE TermNo = 1
AND File = '\\fr\Content\fr_localized_content.xml'
AND Context = '(le second niveau), lequel doit accéder aux ressources d'un serveur de base de données ou d'un partage réseau (le troisième niveau). Le jeton de sécurité principal utilisé entre le navigateur et le s'

In most languages I could add slashes to this string to escape out the single quotes (') in the string.  But I don's seem to be able to do that in PowerShell.

Is there a way I can execute this query within PowerShell and receive an accurate response back from the database?

Thank you.
test-scripts.zip
bgsullivanAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ahoffmannCommented:
for SQL you need to double the single quote
0
BSonPoshCommented:
To answer your question directly
- The escape character in Powershell is backtic "`"
You could do a -replace on the string like this
$string -replace "'","``'"

Probably a better option is to use this script from Lee
http://www.leeholmes.com/blog/InteractingWithSQLDatabasesInPowerShellInvokeSqlCommand.aspx
0
bgsullivanAuthor Commented:
Yeah, i've tried that and I still get errors.  For instance, the following SQL:

SELECT TermNo, File, Context
FROM ExceptionFC
WHERE TermNo = 1
AND File = '\\fr\Content\fr_localized_content.xml'
AND Context = '(le second niveau), lequel doit accéder aux ressources d`'un serveur de base de données ou d`'un partage réseau (le troisième niveau). Le jeton de sécurité principal utilisé entre le navigateur et le s'

Will return the following error:

Exception calling "Fill" with "1" argument(s): "Syntax error (missing operator) in query expression 'TermNo =2 AND File = '\\it\itlocalization.xls' AND Context = '(le second niveau), lequal doit acceder aux ressources d'un serve'." At C:\Temp\test_script_failing.ps1:29 char 22 + [void] $adapter.fill(<<<< $dataset)

When I remove the single quotes from the 'Context' string it works fine.  Any further ideas?
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

BSonPoshCommented:
Where is the code that creates $dataset?

0
bgsullivanAuthor Commented:
I included test scripts that will replicate the error in the origional post.  If you download the ZIP file you will find a working example and a failing example.

Thanks.
0
ahoffmannCommented:
> .. "Syntax error (missing operator) in query expression
sounds like an error from yur db
As I already said: you need to double single quotes in your text *before* you pass it to the database.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
BSonPoshCommented:
I agree with ahoffmann that the error is being returned by SQL.

I would replace the inner single quotes "'"  with double quotes "
-replace "'","`""

or as ahoffmann suggest... double the internal single quotes
-replace "'","`'`'"
0
bgsullivanAuthor Commented:
Sorry for the delay in response but I was in meetings all day yesterday.  The single escape sequence solution does not work but the dual escape sequence does work.  Thank you both for your help.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Powershell

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.