Dear experts -
I have a main form that shows projects (nonupdatable recordset) - and includes some 6 or 7 fields that are complex calculations - some of these call functions that do a fair amount of calculation. Trust me, these fields are a huge benefit, and I explored options of simple queries, but in the end they do need a more complex calculation (e.g., looping through records to determine certain things).
NOW - the issue is - right now, the way the code is written, every time someone comes BACK to this form, it is doing a requery, which while not a deal-breaker, does take a few seconds every time. For a remote user perhaps as long as 5 seconds. Maybe this isn't so terrible.
Anyway, I read about REFRESH instead of REQUERY and this sounded ideal - except that REFRESH doesn't appear to update fields that are calculated from other queries (OR AM I MISSING SOMETHING?).
When i issue a refresh instead of requery command, the record in question isn't appearing properly (it DOES appear properly when the requery command is issued).
Any ideas, or should I just leave well enough alone? One idea I was considering was to remove those calculated fields from recordsource and use dlookup or function call on each record, based on key fields that I would hide on each record. Not sure if this is a good idea or not - would the refresh work in this case?