Re: Oracle8i/ODBC error

Just grasping at straws, but it appears to me that Access analyzes the indexes of a table when it is attached so it can use the information to optimize hybrid queries (actually, it seems to optimize non-hybrid queries too, and often does it very badly). I suspect that Access is making the assumption that any index declarations will be simple column lists, and gets confused when this is not the case).

If you make a view of the table, and attach the view from Access, Access does not get to look at the indexes, and should, thus, not be confused by indexes it would not understand.

On Tue, 17 Oct 2000 20:32:39 GMT, Nhuan_at_Lieu_NoSpam.org <Nhuan_at_Lieu.org> wrote:

>Hi Oracle8i experts,
>
>After we applied several function-based indices on several Oracle8i
>tables, we are no longer able to attach to those tables via Access 97
>like we used to. We received the following error from Ms
>Access97: "invalid field definition 'SYS_NC00116$' in definition of
>index or relationship". "SYS_NC00116$" is an Oracle8i-generated index
>name for the function-based index.
>
>I would appreciate on any help on resolving this. Thanks.
>
>Here's what we have tried: upgraded to the latest Oracle ODBC driver
>from Oracle (see below). Note: access to a table without function-based
>index is still working.
>
>Here are version information on various Oracle product in the NT4
>system:
>
>* Oracle (not Access) ODBC Driver version - 8.01.61.0 with a date of 04-
>28-2000 as seen from ODBC Data Sources on Control Panel. This was the
>latest from Oracle's webite as of this AM.
>
>* Select * from v$version; -->
>Oracle8i Enterprise Edition Release 8.1.6.0.0 - Production
>PL/SQL Release 8.1.6.0.0 - Production
>CORE 8.1.6.0.0 Production
>TNS for 32-bit Windows: Version 8.1.6.0.0 - Production
>NLSRTL Version 3.4.1.0.0 - Production
>
>
>Sent via Deja.com http://www.deja.com/
>Before you buy.
  Received on Tue Oct 17 2000 - 19:46:51 CDT