Re: How can user name/table name concatenation be prevented when using ODBC?

In Article<49mfp0$a55_at_mrnews.mro.dec.com>, <ronald_at_mix004.nwg.dec.com> writes:  

>
> Oracle concatenates user names and table names, for example user "diane" and
 

> table "product_table" becomes "diane.product_table". When the database is
> accessed via ODBC, I would like to access tables using table names (or
 public synonyms) only.
>
> I tried public synonyms. This works if a user logs in into Oracle directly.
> But if access is done via ODBC, these synonyms don't show up in a normal
way. They are only visible if system names are requested also. But system names are not visible if you try to use attached tables with MS-Access 2.0.

Here's one approach, although it's not very pretty:

Create private synonyms in each user's schema, which should allow you to reference the unqualified table names(or views, or procedures) via ODBC. The pain is in maintaining the synonyms. We've developed a script (which must be run as "system") to create all the synonyms we need for each user.

At some point, we were going to look into the use of public synonyms to ease our maintenance work. I'm surprised to hear that public synonyms don't work as expected.