Digital Workshop

I am creating a document database with a simple query (action not script) Sometimes the query is case sensitive, other times it is not, but there seems to be no logic to what triggers it one way or the other, just seems to be random. But once it goes one way or the other, it tends to be consistent.?? Anyone seen this before?

Sandyn,

Have not encountered that in Opus. Have not worked very much with DBs using standard Actions.

However, I can offer this observation.
Using SQLite and the SQLite Manager (Opus not used in this test), I get this Query to run just fine.

If I recall, SQL keywords are not case-sensitive. They are usually typed in all CAPS as a matter of convention for convenient reading. With some testing, it seems that Column Names are also not case-sensitive -- for what is passed to the database as an SQL query.

Data values in quotes or single-quotes, for example in a WHERE expression, are case-sensitive.

I then did a brief Ask.com search on SQLite and "case sensitive" --- it seems 'opinions' are all over the place in the search results. So I am comfortable with my OPINION above.
[Lar EDIT:] There was some mention of differences in handling unicode/international charactersets vs the ASCII range.
[Lar EDIT 2:] This page, from the above Search seems to give some pretty definitive explanation, even covering testing of different SQL DBs. http://www.alberton.info/dbms_identifie ... ivity.html

Thanks!
I'm using the query action, because it's SO easy I have a document database (spreadsheet) and it has dozens of tables and about 20 columns in each table. I'm searching across 12 colums of data in the SQL query. I could never script it without getting very confused with all the names. As usual, Opus makes it so easy.
I thought an SQL query would be case insensitive by default, then you can force it to be case sensitive, but what baffles me is the Opus action changes. Today, it is case sensitive, yesterday, it was case insensitive. There are ways round it, but I would like to understand if it's something stupid I am doing.!

Sandy

I just notice you do not have a Profile/signature
So I have to ask... what version of Opus etc, some system and OS info, and in this case... what Office product/version? Basic stuff.

You might as well email DW.

As a joke, I would say it's a feature. The new 'switch' 'case' feature.

I think case sensitivity is handled by ODBC not Opus. It should, or at least always has been when I've used it, insensitive. I can think of three reasons why it might appear erratic.

a. human error - there is a problem with the query or data
b. the publication has been corrupted - seen this before with database actions.
c. the database source is open else where.

Mack

Of the three possible causes.....C. causes it. If the database is open, the search is case sensitive, if the database is closed, it is case insensitive....Thanks!! I've never seen this before, but it's been a while since I've done a database application.

I didn't really understand a) ??? what is human error??