Did you try
'#PreserveSingleQuotes(Evaluate(ThisField))#%'
-Original Message-
From: John McKown [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 22, 2000 9:51 AM
To: CF-Talk
Subject: RE: SQL Queries on Irish last names that have an apostrophe
That sounds cool. I will che
Dover, DE 19901
email: [EMAIL PROTECTED]
phone: 302-736-5515
fax: 302-736-5945
icq: 1495432
> -Original Message-
> From: Troy Leaver [mailto:[EMAIL PROTECTED]]
> Sent: Friday, December 22, 2000 11:51 AM
> To: CF-Talk
> Subject: Re: SQL Queries on Irish last names that have a
SQL7 Full-text search handles this automagically.
That is, searches for O'Neill without any massaging
of O'Neill to O''Neill, and so forth.
Perhaps Verity does, too. But Verity doesn't
allow standard SQL in the same breath as SQL7
full-text search does. Perhaps the new Verity
K2 will add amazin
9901
email: [EMAIL PROTECTED]
phone: 302-736-5515
fax: 302-736-5945
icq: 1495432
> -Original Message-
> From: Troy Leaver [mailto:[EMAIL PROTECTED]]
> Sent: Friday, December 22, 2000 11:51 AM
> To: CF-Talk
> Subject: Re: SQL Queries on Irish last names that have an apostro
With most SQL databases, you can get around this by escaping the apostrophe with
another apostrophe, so that your query reads:
SELECT *
FROM Lawyers
WHERE 0 = 0
AND LNAME LIKE 'o''donnell'%
I also noticed that your wildcard is outside your string delimiters. I'm
Use the CF function PreserveSingleQuotes() to encapsulate the last name.
-Original Message-
From: John McKown [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 22, 2000 8:48 AM
To: CF-Talk
Subject: SQL Queries on Irish last names that have an apostrophe
I hope this is an easy question
I hope this is an easy question for you SQL gurus.
I am not sure why someone would want an apostrophe in their last name, :)
but I need to know how to get around that when writing SQL queries
that search records for last names contain apostrophes.
Here is a sample query that loops through the se
7 matches
Mail list logo
