Ideas?
Thanks!
Susan
--
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"Susan" <anon...@discussions.microsoft.com> wrote in message
news:031f01c3a3db$fb021990$a401...@phx.gbl...
I turned off the Name Auto-correct, but the results were
the same.
Anything else we can try?
Thanks!
Susan
coddi...@cobrohsv.com
--
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"Susan" <anon...@discussions.microsoft.com> wrote in message
news:029101c3a3e3$93d947e0$a601...@phx.gbl...
--
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"Susan" <anon...@discussions.microsoft.com> wrote in message
news:057101c3a3e9$0a08eb50$a301...@phx.gbl...
It covers a range of issues including Name AutoCorrect (as Kevin3NF
mentioned), the caching of the table links, the setting of table's
SubDatasheets, etc.
--
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.
"Susan" <anon...@discussions.microsoft.com> wrote in message
news:031f01c3a3db$fb021990$a401...@phx.gbl...
Susan
It is so slow that you can see the value of each field
come up separately ... maybe a few seconds total, but
definitely not like the "big bang" fill we were getting
before the split. And then each time we update, we get
the same slow filling of the form.
Everything else on the network runs quickly?
--
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"Susan" <anon...@discussions.microsoft.com> wrote in message
news:0bf901c3a47b$af3cdcc0$a601...@phx.gbl...
>.
>
In the filling of the form, we were using a function
(DCOUNT) which worked just find when the database was
one. When we split it, the performance went way down.
We replaced the DCOUNT call with an equivalent SQL
statement that counted the records as desired. And wa-
la ... the form is filling fast again.
So I guess the lesson learned is that for performance
reasons we should use functions only as a last resort.
Thanks for all of your help and interest!
Susan
The domain aggregrate function such as DSum(), DCount(), DLookup() are slow.
It's interesting that the difference was the significant factor in your
case, and that the difference was more significant after splitting.
Tony, if you are reading this, you might want to consider adding this to
your page at:
http://www.granite.ab.ca/access/performancefaq.htm
--
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.
"Susan" <anon...@discussions.microsoft.com> wrote in message
news:016d01c3a48d$6f3e1730$a301...@phx.gbl...
>Ok, I think we've solved it ... so I wanted to make sure
>that I let you all know what we found.
Much appreciated. Thanks for posting your solution.
I received Allen's email, thanks Allen, and have updated my Access
Performance FAQ page accordingly. A link to this thread and a thanks
to Susan has been added.
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
(snip)
> Second, create a table ( I called mine "Keep Open" with only one field and
no data.
FYI, you don't need the table. Just open a reference to the BE database
using OpenDatabase().
HTH,
TC
>> Second, create a table ( I called mine "Keep Open" with only one field and
>no data.
>
>FYI, you don't need the table. Just open a reference to the BE database
>using OpenDatabase().
Hmmm, now there's another idea.
It works fine - as long as the reference variable stays in scope for the
whole run :-)
TC
>It works fine - as long as the reference variable stays in scope for the
>whole run :-)
Oh yeah, I'd forgotten that one. That's why I prefer a, usually
hidden, form open at all times.