Re: VB app connectivity problems with Oracle 8i Server

I've never encountered that in other uses of ODBC ( and when linking or importing Oracle from Access ) .. So this is just a thought - be sure to use a fully qualified table name in all references ( schema.tablename ) and be sure the user connecting thru ODBC has directly granted rights to those tables - maybe the ODBC connection thru VB does not handle role-granted rights ( if that even applies in your case)... ( as a personal note, I try to avoid public synonyms - Just a quirk, but I find it hard to track permissions with them around)

hth    

"Priyesh Patel" <priyesh_at_mercurie.co.uk> wrote:

>Hi,
>
>I am trying to migrate an existing VB application so that it uses Oracle
>instead of access database. I am using ODBC
>to connect the application to the oracle server.
>
>I have observed two problems :
>
>a). VB application complains about tables not found if public synonyms are
>created.
>
>b). Similar problem if more than one user has a table with the same name.
>
>The VB application works fine if there are no synonyms and if only one
>schema exists in the database.
>
>Has anyone else encountered this problem ? I have tried the Oracle supplied
>ODBC driver and Microsoft's.
>
>I would be grateful for any advice.
>
>Regards
>Priyesh
>
>Mercurie IT
>
Received on Tue Apr 02 2002 - 18:17:19 CEST