The domain aggregate functions would be the simplest to implement, though
performance will be woeful if you have 3 per record and multiple rows.
DMax() should return the highest value or the most recent date. If you want
the value from one field sorted in descending order by another field, you
could use this extended version of DLookup():
http://allenbrowne.com/ser-42.html
If your user only really needs to see the extended information for the
selected row of the continuous form, you could put the extra text boxes in
the Form Footer section, looking up the extra fields with a series of
calculated controls or even a listbox or a datasheet subform. That would
solve the performance issue.
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"S P Arif Sahari Wibowo" <arifsaha@yahoo.com> wrote in message
news:Pine.LNX.4.63.0601171828170.1667@localhost.lo caldomain...[color=blue]
> Hi!
>
> I would like to make an editable continous form, where most fields will be
> from table A and editable, except 1-3 fields are a glimpse into table B
> and uneditable. Table A relate to table B in one-to-many relation. I don't
> need to see all values in B that relate to the particular record in A,
> just one value in each field in B, preferably the last entered.
>
> This is to ease a person that need to manually fix and encode some of the
> records.
>
> However, this means an aggregate value (last) upon B's fields side by side
> with values from table A. This render the query uneditable and hence the
> form also uneditable.
>
> I tried to work on it the form itself using unbounded fields, but since it
> is a continuous form, obviously each time the value in the unbounded
> fields change, it change in every display of the record. So it doesn't
> work.
>
> I tried the aggregate functions, but it quite a performance hit, and there
> is no DLast.
>
> I am thinking to use a "scratch" table to contain temporary value of the B
> table, but since the operator may jump to other forms to edit value in B
> as well, means the scratch table will have to be rewritten avery time that
> happen.[/color]