From: | Walter Willmertinger <willmis(at)gmail(dot)com> |
---|---|
To: | pgsql-odbc(at)postgresql(dot)org |
Subject: | Fwd: Error using odbc 11.00.0000 |
Date: | 2018-11-20 14:21:34 |
Message-ID: | CAHbMG0XKvxJZwVX=qvX5zSNARjo+sZSVd1BSzkLaRPXwNkz9+Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-odbc |
After installation of this new release we have follwoing problem in an MS
ACCESS project.
In a form there is a search window where a user can enter a search string.
The data source for this form is following query:
SELECT Interessenten.[ID]
FROM Interessenten
WHERE ((([Name] & ',' & [Vorname]) Like '*Ritter*')) OR
(((Interessenten.Ort) Like '*müller*')) OR (((Interessenten.PLZ) Like
'*müller*')) OR (((Interessenten.Handy) Like '*müller*'));
This query leads to an exception:
ODBC Call failed (in german)
ERROR: function concat(text,text) does not exist:
Error while exection the query(#1)
If I omit the concatenation: ([Name] & ',' & [Vorname]) Like '*Ritter*'),
the query is executed normally.
Environment: ODBC 64 Bit, Windows 10, Access 2013
I already activated
Regards
Walter Willmertinger
From | Date | Subject | |
---|---|---|---|
Next Message | Melanie Plageman | 2018-11-20 20:24:59 | Re: BUG #15160: planner overestimates number of rows in join when there are more than 200 rows coming from CTE |
Previous Message | Walter Willmertinger | 2018-11-20 13:29:59 | Error using odbc 11.00.0000 |
From | Date | Subject | |
---|---|---|---|
Next Message | Inoue, Hiroshi | 2018-11-21 05:32:21 | Re: Fwd: Error using odbc 11.00.0000 |
Previous Message | Walter Willmertinger | 2018-11-20 13:29:59 | Error using odbc 11.00.0000 |