Trying to use UCanAccess to recreate functionality previously implemented with jdbc/odbc drivers. For a long time, we've had code that is used to do a complete nightly refresh of some fairly large tables. Basically, we DROP the tables from the Access DB, then use DDL to recreate the table, then populate the tables with fresh data.
Because (apparently) there are, indeed, queries in the Access DB that are built against data in the tables, the DROP command results in, for example, ERROR: net.ucanaccess.jdbc.UcanaccessSQLException: UCAExc:::5.0.0 java.sql.SQLSyntaxErrorException: dependent objects exist: PUBLIC.QRYJDPSDOGLEADS in statement [DROP TABLE tblRelationshipTableLOCAL].
So...I get it, there's a dependent query. But I can open that Access DB at any time and delete the table without Access objecting at all. Is there a way for me to "force" this DROP without regard to the dependent objects/queries?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Trying to use UCanAccess to recreate functionality previously implemented with jdbc/odbc drivers. For a long time, we've had code that is used to do a complete nightly refresh of some fairly large tables. Basically, we DROP the tables from the Access DB, then use DDL to recreate the table, then populate the tables with fresh data.
Because (apparently) there are, indeed, queries in the Access DB that are built against data in the tables, the DROP command results in, for example, ERROR: net.ucanaccess.jdbc.UcanaccessSQLException: UCAExc:::5.0.0 java.sql.SQLSyntaxErrorException: dependent objects exist: PUBLIC.QRYJDPSDOGLEADS in statement [DROP TABLE tblRelationshipTableLOCAL].
So...I get it, there's a dependent query. But I can open that Access DB at any time and delete the table without Access objecting at all. Is there a way for me to "force" this DROP without regard to the dependent objects/queries?