Re: Continuous Form code for current record
- From: "Linq Adams via AccessMonster.com" <u28780@uwe>
- Date: Mon, 31 Mar 2008 13:53:49 GMT
I'd also be interested in seeing a calculation that slows down your form's
opening to such an extent! How many records are we talking about here?
Your only options in a continuous form are, as suggested, to do the
calculations in the query or to store the calculation results in a bound
field. And before someone chimes in, as they always do, yes, storing
calculated results in a table is frowned on by many, but there are instances
where it's allowable! They're even circumstances where it's absolutely
necessary! You just have to weigh pros and cons and decide if the trade-off
is worth it to you; speed versus storage space.
--
There's ALWAYS more than one way to skin a cat!
Answers/posts based on Access 2000/2003
Message posted via http://www.accessmonster.com
.
- Follow-Ups:
- Re: Continuous Form code for current record
- From: BruceM
- Re: Continuous Form code for current record
- References:
- Continuous Form code for current record
- From: Question Boy
- Re: Continuous Form code for current record
- From: BruceM
- Re: Continuous Form code for current record
- From: Question Boy
- Re: Continuous Form code for current record
- From: BruceM
- Continuous Form code for current record
- Prev by Date: Today's date and add 365 for second date?
- Next by Date: Re: Continuous Form code for current record
- Previous by thread: Re: Continuous Form code for current record
- Next by thread: Re: Continuous Form code for current record
- Index(es):
Relevant Pages
|