David W. Fenton said:
Sounds like a case where the fragmentation causes the data retrieval
for the reports to cross a threshold. Interesting case, and exactly
the level of activity that would cause me to suggest backup/compact
on a daily basis.
I think that even if he compacts it in the morning that the 1500
records are enough to require another compacting.
Sure, but it's probably running pretty well when you compact, right?
I know I've always been amazed at exactly how well Jet performs
under high loads -- it can go on problem-free for years after you've
crossed into upsizing territory.
Oh yes, it does perform quite well. Most of the other users from
nearby provinces come in via Terminal Server and it works well.
There are some very interesting techniques we are doing from a UI
perspective that I'd like to document. Trouble is it would take me
several days of solid work to do it justice.
For example the unbound time sheet entry form has about 5,000 lines of
code behind it validating the data. You can enter up to three
regular, overtime and/or double time transactions on the one form with
all the other data being identical. Then standard "add-on"
transactions are also created of which there could be 5 or 6 on each
transaction.
Then we have a popup form that lists all the just added transactions
so you can go back and edit them in a new copy of the unbound data
entry form just to do a bit of cleanup. All the while leaving the
original data entry open.
Etc, etc, etc.
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
Tony's Microsoft Access Blog -
http://msmvps.com/blogs/access/