From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Brad White <b55white(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Quoting issue from ODBC |
Date: | 2023-02-08 00:23:49 |
Message-ID: | CAKFQuwZv0ZtOa+NiZP1E+C-B+EPQCieZ-UJtcReXWUETrOsqSA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-odbc |
On Tue, Feb 7, 2023 at 5:20 PM Brad White <b55white(at)gmail(dot)com> wrote:
> For example, this is the literal code in VBA
>
> Access: connection.Execute "UPDATE [" & strTable & "] SET [" & strTable &
> "].[InsertFlag] = Null" _
> & " WHERE ((([" & strTable & "].[InsertFlag])=" & lngCurrUID & "));",
> , adCmdText Or adExecuteNoRecords
> Note that InsertFlag is bracketed the same way in both instances.
>
> PSQL: UPDATE "public"."Orders" SET InsertFlag=NULL WHERE ("InsertFlag" =
> 166 )
> Note that InsertFlag is quoted once but not the other time.
> Of course this gives the error: column "insertflag" of relation "Orders"
> does not exist at character 35.
>
>
Either VBA is doing some query munging or that concatenated string isn't
the one that is producing the error. Which suggests that maybe you have a
string somewhere that is not written correctly that need to be fixed so it
doesn't produce this error.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Rob Sargent | 2023-02-08 00:32:52 | Re: Quoting issue from ODBC |
Previous Message | Brad White | 2023-02-08 00:19:56 | Fwd: Quoting issue from ODBC |
From | Date | Subject | |
---|---|---|---|
Next Message | Rob Sargent | 2023-02-08 00:32:52 | Re: Quoting issue from ODBC |
Previous Message | Brad White | 2023-02-08 00:19:56 | Fwd: Quoting issue from ODBC |