D
Dr Frankenstein
This is sort of both a queries and a forms question.
I have a query in Access 2003 that relies on two tables and another
query (we'll call it "the subquery"). Basically the relation is as
follows: Query: table (FK)->(PK) another table (FK)->(PK) subquery.
(The subquery operates only on one table) No fields in the "other"
table are actually displayed; it is only there because one of its
fields is used in the relation.
The query has some calculated fields that rely on the subquery. When
the user inputs data in the form that is based on the query (or just
the query's datasheet), the calculated fields that rely only on the
table are populated as data becomes available from the user. However,
calculated fields that rely both on the table and the subquery are not
populated on input (they stay blank), nor even when the record is
saved; they are only when the query (or form) is closed then reopened.
Hitting F9 (or calling Recalc() from VB) does not fix it. The problem
is that the calculated data must be available to the user (and also
the application) for validation purposes.
Is there something I can do with the form, queries and/or tables so
that, at least in the form, the fields can be properly computed before
the record is saved, or do I have to reimplement the calculated
controls in VB with DLookup?
I have a query in Access 2003 that relies on two tables and another
query (we'll call it "the subquery"). Basically the relation is as
follows: Query: table (FK)->(PK) another table (FK)->(PK) subquery.
(The subquery operates only on one table) No fields in the "other"
table are actually displayed; it is only there because one of its
fields is used in the relation.
The query has some calculated fields that rely on the subquery. When
the user inputs data in the form that is based on the query (or just
the query's datasheet), the calculated fields that rely only on the
table are populated as data becomes available from the user. However,
calculated fields that rely both on the table and the subquery are not
populated on input (they stay blank), nor even when the record is
saved; they are only when the query (or form) is closed then reopened.
Hitting F9 (or calling Recalc() from VB) does not fix it. The problem
is that the calculated data must be available to the user (and also
the application) for validation purposes.
Is there something I can do with the form, queries and/or tables so
that, at least in the form, the fields can be properly computed before
the record is saved, or do I have to reimplement the calculated
controls in VB with DLookup?