Re: Using calculated fields in multiple queries

Tech-Archive recommends: Fix windows errors by optimizing your registry

Yes, the non-calculated fields also get locked in the queries. Let me check
the relationships between the table and the basic query...

"JohnFol" wrote:

> A calculated field is always locked.
>
> Do you mean that non-calculated fields are also locked? If so this is more
> likerly to do with the joins / relationships between the tables that the
> calculations.
>
>
>
> "Linguist" <Linguist@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:A7B7A871-F902-49F3-A111-9C878481DF13@xxxxxxxxxxxxxxxx
> >I have a database with one basic table. I have several different queries
> > querying the table for different criteria. I am using the data*** view
> > of
> > these queries to enter / update values in certain fields.
> >
> > All these queries, however, use calculated fields that are the same for
> > any
> > of the queries. I could create these calculated fields for each of the
> > queries separately. But the calculations behind the calculated fields are
> > quite complex, and there are many calculated fields. Therefore, I thought
> > I'd
> > create a basic query that contains all these "shared" calculated fields I
> > need for the other queries. This way I could maintain and modify the
> > calculated fields in one location and reuse them in multiple queries.
> >
> > So I created a Basic Query containing the fields Calculated1, Calculated2
> > etc. Then I created QueryA, QueryB, QueryC. For each of them, I added both
> > the basic Table and the Basic Query, and I added the fields Calculated1,
> > Calculated2. Everything works fine, the fields and correct values are
> > shown
> > in the data*** view of my queries, but: All records are locked.
> >
> > What should I do differently?
> >
> > Many thanks in advance for any help!
>
>
>
.

Quantcast