Re: case sensitive object names via ODBC

On Sep 7, 4:50 pm, Mark Lemoine <mark.a.lemo...@xxxxxxxxx> wrote:
On Sep 7, 4:43 pm, "fitzjarr...@xxxxxxx" <fitzjarr...@xxxxxxx> wrote:





On Sep 7, 3:36 pm, Mark Lemoine <mark.a.lemo...@xxxxxxxxx> wrote:

I've been assigned to support a legacy app that we have that's coded
in VB4 (16bit) that connects to an Oracle db via ODBC. Everything is
fine in the production environment, my problem is in the test db
environment that I'm trying to setup.

I got a script from the dba from the production db to create the
tables, etc. I run that script on my test db and that''s fine. But,
when I try to perform a select from my code:

Select * from Translation

I get an error back something like "query or table not found" (sorry,
I didn't write down the exact msg). When I change the query to:

Select * from TRANSLATION

It works fine. This is connecting thru an ODBC dsn using DAO (hey - I
did say that it's legacy!). The table names in the script are not
quoted (so they should be case-insensitive).

If I run SQL*Plus, then the table name is not case sensitive (that is,
Translation or TRANSLATION works), so this is something just with my
ODBC setup, I conclude.

Can anyone help? What's wrong with what I'm trying to do?

Thanks
Mark

One guess is that it may be how the ODBC/DAO piece 'transliterates'
the script. You'll know that by querying V$SQLTEXT and looking for
your queries; you may well find the table names wrapped in quotes even
though they aren't in the source script.

Just a thought.

David Fitzjarrell- Hide quoted text -

- Show quoted text -

Yup, that's it. When I look at V$SQLTEXT, I can see quotes around my
table reference, ie 'Translation'.

I'm using the Oracle v9 odbc driver. I don't see any options on the
dsn setup to control this behavior.

Any ideas on how I turn this off? Or a different odbc driver to use
(at this stage of the app's life, converting from odbc to something
else isn't an option)? (I am checking to see what's configured on
the working-fine-in-production workstations).

Thanks!
Mark- Hide quoted text -

- Show quoted text -

Yet ANOTHER guess is it isn't the ODBC driver causing your problems,
it's VB4. I use the Oracle ODBC/OLEDB drivers and experience no such
problems, even when using Abscess as a front end (not my choosing,
believe me).


David Fitzjarrell

.

Relevant Pages

  • Re: ORACLE DRIVER
    ... Not sure I understand why you need ODBC Cyril. ... I'd point you again to the native Oracle DBD ... So is there any free Oracle ODBC driver for Linux? ... UnixODBC is a freeware but couldn't find any free Oracle Drivers. ...
    (perl.dbi.users)
  • Re: Whats so bad about ODBC
    ... It is far better to connect to Oracle using the native connectivity. ... What exactly might be a problem with ODBC? ... data to be fetched to the client, and have it filtered on the client. ... actual execution paths are often unpredictable, ...
    (comp.databases.oracle.server)
  • Re: The Oracle ODBC driver story
    ... There are many pieces of software that use ODBC. ... do acknowledge the bug but essentially say "go ask oracle why are they ... into an open source reporting engine called RLIB. ... RLIB is an engine that can produce PDF and HTML reports, ...
    (comp.databases.oracle.server)
  • Adding Oracle driver crashes MS ODBC adminstrator
    ... I'm trying to set up the new Oracle 10g ODBC driver and it seems to be ... crashing the MS ODBC Data Source Administrator. ...
    (microsoft.public.data.odbc)
  • RE: Windows to Oracle
    ... resolved yet (with respect to a Windows OS). ... and Oracle DBDs. ... Need to install Oracle on your own machine before you can connect to the ... If you are truly trying to use ODBC, why are you specifying the Oracle ...
    (perl.dbi.users)