Predicate for non-updateable query...

[cheuschober]

Okay, it may seem like a silly question for one who's been using this as long as I but I was just curious if anyone had a concise answer as to the predicate for a non-updateable query?

Today I think I decided to stop using a workaround by creating a temporary table with duplicate information found elsewhere in the system.

~Chad

 

[Pat Hartman]

Queries are non-updatable for a variety of reasons. You can find more details in help but I'll list a few of the most common here:
1. Aggregate functions. Even if it seems as though Jet should be able to identify an individual record (you join tblA to a query that aggregates tblB and you want to update a field in tblA) the rule is that no query containing aggregation is updatable. I requested this specific example as a possible update to Jet from the Microsoft development team. We'll see if it happens.
2. Improper Joins. These fall into two types - cartesian products and multiple, non-hierarchial 1-many joins in a single query.
3. insufficient permissions on one or more of the tables. If all tables are not updatable, none of them are - see problem 1.
4. Inability to determine the cardinality of a relationship because one or more of the tables does not have a primary key.
5. Linked ODBC tables MUST have primary keys (or psuedo keys) defined to allow update.