Chuck,
If you click on Help in 7.6 and Search for IDQUOTES it gives you a pretty
complete explanation of what IDQUOTES does. Here is what it says;
***************************************
IDQUOTES
Operating Condition
Syntax: SET IDQUOTES
Default: 7.6: Back Quote (`) Prior: NULL
Controls the character that is used to set off object names.
IDQUOTES sets the character for enclosing object names, such as column or
table names, in R:BASE and ODBC commands. This is especially critical when
using ODBC to connect to a non-R:BASE Database that allows characters such
as spaces in Column or Table names. This is also critical to SOME internal
R:BASE processing.
Note: Older databases may default to NULL which is not ODBC or SQL
compliant.
In general, setting IDQUOTES will have no effect on legacy applications as
they will not, in most cases, know that this exists. The one exception to
this is UNLOADing data from a database that has IDQUOTES set, such as an
upgraded R:BASE 2000 database, and importing into a Legacy database. If you
are attempting to do this you should set your IDQUOTES to NULL.
The Back Quote is the Reverse Single Quote that is located, on most standard
US Keyboards, under the Tilde (~) character and to the left of the numeral
1.
*******************************************
It looks like your problem with ODBC connections is directly attributable to
the idquotes setting. You can correct this in your legacy database by
issuing aSET IDQUOTES="`" (assuming your quotes=").
BRO commands for integer datatypes don't need quotes, but text datatypes
definitely need them. The quotes setting should be the same in both
databases. I have found in older databases that the idquotes is usually
null. When transferring data, I make sure that the character settings in
both databases are identical and the idquotes setting should be set to `.
It could also be that triggers, rules or computed columns in tables in one
or both of the databases have imbedded double quotes. This would create
problems if the quote setting for the database is set differently. I would
look for them and eliminate them if you decide to use single quote '. Quote
settings, delimiter and idquotes settings should be the same in both
databases.
Hope this helps.
Bill Eyring
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Wednesday, November 05, 2008 6:37 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Round 2 - ODBC Error Unrecognized column inexpression
I have identified what going on. I 'm hoping someone can help me with a
solution.
I've been using rbase from way, way back. Because of our old code we still
use quotes ="
Both of my databases use quotes = ". A BRO command that does not use quotes
in the search works fine. (i.e. search for an integer). If I connect to the
rbase DB that I want to attach to and change to quotes = ' and then disc
and connect to my receiving db the query works fine (leaving quotes = " on
the receiving database).
I don't understand the function of Idquotes and documentation is sparse ,
but when I change to IDquotes = " on the DB I'm attaching to, the BRO query
it works fine. Unfortunately rbase will not allow me to set Idquotes = "
and Quotes = " (I suspect that this would also wreck havoc with my Microsoft
SQL ODBC queries). Does anyone have any suggestions for me? Is there
documentation on Idquotes I'm not finding?
I truly do appreciate all the help that be given to me here and when a
question in my area of expertise (Telecommunications & Infrastructure) is
posted I have always tried to answer thoroughly and I do understand how much
unpaid time it takes to help people out.
