Access appears to hang when linking Oracle table via ODBC

[bdtmike]

I'm using Access to view data from an Oracle 9i database. When I try
to link an Oracle database, the PC appears to Hang before finally
presenting the list of tables to choose from. It's a large Oracle
Database (lots of objects) and I know it's pulling every object over to
make up this list. It may take as long as 3 minutes of waiting before
seeing the table list. Is there a workaround/configuration setting for
this?

[billmiami2]

3 minutes is a long time, but I seem to remember having to wait quite a
while for the object listing with databases that had a lot of objects.
Do you need access to all of those objects? If not, you might try
associating only a limited set with the user that you're using for
accessing the Oracle database.

Also, this is an operation that is normally done only once, unless
you're deleting the links after you create them. I wonder why you
would need to do it repeatedly.

If you do need to do it repeatedly and you can't solve the problem any
other way, you could code your own utility that gets the list of the
objects (tables, views) from one of the system tables. The user could
click on each desired object and you could create a linked tabledef in
code with the appropriate connection string.

Bill E.

[Tim Marshall]

bd*****@hotmail .com wrote:

I'm using Access to view data from an Oracle 9i database. When I try
to link an Oracle database, the PC appears to Hang before finally
presenting the list of tables to choose from. It's a large Oracle
Database (lots of objects) and I know it's pulling every object over to
make up this list. It may take as long as 3 minutes of waiting before
seeing the table list. Is there a workaround/configuration setting for
this?

This is a bother for me too, though I tend to use PTQs and DAO most of
the time, so don't bother with linking tables unless I am doing Oracle
database administrative type tasks.

One thing that may or may not help, might be to set up an Oracle user
with just the tables that you want. Going through that user instead of
the sysadmin user or whatever might be faster.

Other than that, I don't know what to tell you.
--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Whatcha doin?" - Ditto "TIM-MAY!!" - Me