Updateable Query

[JimS]

I have a subform that displays budget rows. It's keyed on Project and
Discipline IDs. It displays % complete and Budgeted Hours in a simple
datasheet. Worked fine. % comlete and Budget hours were both updateable.

I added a couple fields to the subform's data source with a left join to an
aggregate query. I don't want to update the new fields, just the old ones.
but now the query appears not to be updateable. So, I changed the extra
columns to be drawn from the aggregate query using a domain aggregate
function (dlookup). Query is now updateable, but very very slow.

Ideas?

 

[Golfinray]

The first thing I try is to go into that query, change it to a make-table
query, run it and make a table out of those aggregate tables, and then use
the table to either make a new query or use as the recordsource. Aggregate
queries always are slow until I do that.

 

[John W. Vinson]

The first thing I try is to go into that query, change it to a make-table
query, run it and make a table out of those aggregate tables, and then use
the table to either make a new query or use as the recordsource. Aggregate
queries always are slow until I do that.

ummmm...

and your data is always out of date and incorrect if you use the MakeTable
query, until you run the MakeTable query again... which is *much slower* than
the aggregate query!!!

 

[John W. Vinson]

I have a subform that displays budget rows. It's keyed on Project and
Discipline IDs. It displays % complete and Budgeted Hours in a simple
datasheet. Worked fine. % comlete and Budget hours were both updateable.

I added a couple fields to the subform's data source with a left join to an
aggregate query. I don't want to update the new fields, just the old ones.
but now the query appears not to be updateable. So, I changed the extra
columns to be drawn from the aggregate query using a domain aggregate
function (dlookup). Query is now updateable, but very very slow.

Ideas?

No aggregate query, nor any query including an aggregate query, is ever
updateable. Could you perhaps display the totals from the aggregate query in a
separete subform?