In designing a utility to load data into Oracle using Visual Basic as a
front end, problems arose in trying to read into the proper tables.  These
problems can be summarized in the following paragraphs, taken from Oracle7
ODBC Driver (Release January 1995) and Visual Basic 3.0 Documentation:

PROBLEMS WITH RUNNING A QUERY ON A USERNAME QUALIFIED TABLE VIEW:
When you type from any Visual Basic or Microsoft Access application,
select * from SCOTT.EMP, the query terminates with the following error
message, "Couldn't find 'USER.MDB'.  Error #3024".  Microsoft Corporation
is aware of this limitation with the application Visdata of Microsoft
Visual Basic 3.0.

PROBLEMS WITH SYNONYMS:
The JET layer is unable to distinguish between two objects of the same
name.  This raises problems with synonyms such as SYSTEM.EMP and
SCOTT.EMP.  Moreover, Oracle7 public synonyms are returned by the ODBC
driver as belonging to "PUBLIC".  Visual Basic does not display the owner
as PUBLIC.  This causes resolution conflicts between a synonym like
ALL_TABLES and SCOTT.ALL_TABLES.

Is there a fix or a work around to these problems?  Any solutions or
suggestions would be greatly appreciated.