Discussions
Categories
- 196.7K All Categories
- 2.2K Data
- 235 Big Data Appliance
- 1.9K Data Science
- 449.8K Databases
- 221.6K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 549 MySQL Community Space
- 477 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 532 SQLcl
- 4K SQL Developer Data Modeler
- 186.9K SQL & PL/SQL
- 21.3K SQL Developer
- 295.4K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.1K Development Tools
- 104 DevOps
- 3.1K QA/Testing
- 645.9K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 153 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 17 Java Essentials
- 158 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 203 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 395 LiveLabs
- 37 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.6K Other Languages
- 2.3K Chinese
- 170 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 230 Portuguese
ODBC linked table issue in MSAccess - possible ODBC driver bug
I am using ODAC 12c Release 2 32-bit (latest) to connect to an Oracle 11g R2 database from MSAccess (Office 2010) 32 bit.
I created an ODBC linked table in Access. What I noticed is that when renaming a column in Oracle and then refreshing the linked table in Access (using Linked Table Manager), the changes are not picked-up.
So I have a table partitioned by range and changed a field name from UNIQUE_CUSTOMER_MAPPING_ID to UC_MAPPING_ID. This is a VARCHAR2 data type.
Access will not refresh the column name and return an error saying this is an unknown field, I had to delete the table and re-add it.
What is weird is that I never had this problem before. It occurred after I changed the table partitioning.
Before it was by an integer:
PARTITION BY RANGE (import_id) (
PARTITION p0 VALUES LESS THAN (2),
PARTITION p1 VALUES LESS THAN (3)
After it was by a date:
PARTITION BY RANGE (start_date)
INTERVAL(NUMTOYMINTERVAL(1, 'MONTH'))
Must be a bug in the ODBC driver, can anybody reproduce this problem?
Thank you,
M.R.