Odd Oracle ODBC error

[dgmoore]

I have an Access 2K app linked to an Oracle 9i back end. When I attempt
to open some - but not all - of the linked tables in datasheet view I
get a Jet "ODBC error" message. I can see nothing in common among the
tables with and without errors, either in number of rows or number of
fields. Queries on these same tables work correctly. Does anybody know
what's going on with this?

Thanks
Dave

 

[Lynn Trapp]

If you are using the same driver in all cases, then I would check out
permissions on the Oracle side.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Big List: www.ltcomputerdesigns.com/JCReferences.html

 

[Joe Fallon]

Opening a table exposes all the fields.
A query only uses some of them.

Some fields do not translate well from Oracle to Access.
By "avoiding" them in the query, it works.

 

[dgmoore]

Joe,

I would think that

select * from [tablename]

exposes all of the fields in the table, and a select * pass-through
query returns the data correctly, while viewing the same table in
datasheet view returns the ODBC error. Wierd...

Thanks
Dave

 

[dgmoore]

Joe,

I would think that

select * from [tablename]

exposes all of the fields in the table, and a select * pass-through
query returns the data correctly, while viewing the same table in
datasheet view returns the ODBC error. Wierd...

Thanks
Dave

 

[Lynn Trapp]

In a pass-through query the server side database does all the processing and
just returns the results to Access. With a linked table Access has to make
sense of all the field datatypes and it can't always do that. That is Joe's
point.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Big List: www.ltcomputerdesigns.com/JCReferences.html