Insufficient base table information for updating

Hans Up is suggesting the database structure is not optimal.

As a practiced diagnostician (mostly diagnosing my own problems, I confess), I think that's very likely true.

In the course of a complex database structure, I need to provide the user with a means of editing data stored in a series of tables.

Although all the data types are the same, they don't line up 1:1 in their names.

When Access combines rows from different tables in a union query, the individual rows lose their underlying table identity. Execute End Sub Insert Data Punk "Table2", 7, "Doo Dar" Provided that the ids are not overlapping then you could restructure your tables to have a parent table containing the ids and child tables containing the data. Id The VBA method would work; however, I'm only a summer intern, and I'll be passing off this project in a week and a half, so I'm trying to make it as easy to maintain as possible; I guess such a solution isn't tenable with this software, and I'll have to stick to the current model of separate edit interfaces."You could probably work around this using VBA and ADO to update the corresponding table" -- have you tried? With a client-side cursor and batch optimistic locking I get an error, "Insufficient base table information for updating or refreshing." Using a server-side cursor and optimistic locking I get a silent failure. My preference would be to consolidate those individual tables into a master table.Turning on the diagnostic trace in the ODBC data source (the one labeled Enable trace on the Diagnostic tab) will produce a log that lists the errors that might have been suppressed by the application. The application might also be attempting to use optimistic locking.In these situations, the application is actually deleting and updating records by running an UPDATE or DELETE SQL statement that has "WHERE too many indexes or too many fields in the unique key.This behavior is encountered in Oracle version, and the first CPU to report this behavior was the October 2014 patch.This bug applies to all Arc GIS releases connecting to an Oracle instance with the applied Oracle permission change.