Patrice - When I've had ODBC problems, only one solution has worked for me: Find another ODBC driver. I've had better luck recently with the Microsoft drivers.
Dennis Williams DBA Lifetouch, Inc. [EMAIL PROTECTED] -----Original Message----- Sent: Friday, October 24, 2003 2:09 PM To: Multiple recipients of list ORACLE-L 1st problem One of our clients' PCs which are still running Access97 can't connect to Oracle 8i via ODBC drive 8.00.61.00. This is the first ODBC driver for Oracle 8.0.6, it is known to be buggy. We cannot upgrade the ODBC drivers on all the clients though, that is done by another group. The user can invoke the Data Source, and see a list of the objects presumably available to connect, but as soon as one of them is selected ODBC fails. The developers suspect suspect it could be because of the sheer number of objects in the database, esp. the number of java classes: There are 9974 java classes in the SYS schema. Total objects count is 38640. Our production db doesn't have as many, 6442 java classes only. That brings our total number of objects to a mere 35845. The client PC can connect to this one using Access97 and the 8.00.61.00 ODBC driver. The developers tell me they confirmed that they also cannot connect with this driver using Access2000. We know it's the driver. I already know that one can get around this problem by creating an ALL_OBJECTS view in the user account's schema, to mask the java classes from the listing, but the idea of replacing data dictionary views manually in people's schemas is leaving some people here a bit uncomfortable. Is there a way to weed through the java classes, and remove the ones that are never used from the database? (I am throwing that in as a lark) Is there a data dictionary view that helps manage Java components like there are for PL/SQL stored objects? If Java is in the database, presumably it's possible to see how the java objects are used, where they are, etc. from the data dictionary? A last access time would be a nice feature. 2nd problem The current Microsoft driver for Oracle can connect to both databases. We had another problem with Access97 using the ODBC driver that comes with Office97. Access97 doesn't see the prefix to table names, including those belonging to public. Because of that, in the list we can end up with duplicates and Access panics when it sees that not all items listed are unique. It becomes so hysterical that users can't even tell it to calm down and point it to an item in the list. Oracle Support confirmed for me that the problem doesn't exist on Access2000, they suggested I upgrade since Microsoft doesn't support Access97 anymore. We can't upgrade Access before June 2004, there are so many PCs to upgrade that this individual's PC won't get upgraded before then. Patrice. -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Boivin, Patrice J INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: DENNIS WILLIAMS INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
