Does having lots of Requeries affect the performance of a database

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a database where I'm continually applying Me.Requery to fields and or
pages.

Can you over do this?

If I have this applied to lots and lots of pages and fields all within one
tabbed menu structure will this have any affect on performance or the
reliability of the database or is this fine?
 
I have a database where I'm continually applying Me.Requery to fields and or
pages.

Can you over do this?

Very easily.
If I have this applied to lots and lots of pages and fields all within one
tabbed menu structure will this have any affect on performance or the
reliability of the database or is this fine?

Every Requery will go back to the tables, rerun the query, and empty
and then repopulate the Form. This takes quite a lot of time. I
wouldn't expect it to affect database stability, but it certainly
won't help performance!

I'll requery a form, but only when I know that something which I have
done in code makes the data now on the form invalid. On a tabbed form,
I'll sometimes leave the Subforms or other controls on the tab empty
(with blank Recordsource properties for the subform) and only set the
recordsource - thereby populating the form - in the tab control's
Change event. Requerying a subform which nobody's going to look at is
a real waste!

John W. Vinson[MVP]
 
John that makes a lot of sense and I thank you for your reply.

The problem is, the person who the database is for has come up with all
these eventualities that have to be planned for. For instance part of my
database is a phone log system, a call is entered into the database and then
goes to the person's inbox for whom the call was intended. But if that person
wants to send that call onto another person, then I have to run a requery on
the field which might be changed, but then to make sure that the person who
the call has been redirected receives, I have to requery every single
person's inbox so that the call appears there without them having to close
and re-open.

Is there a more effective way of doing this?
 
John that makes a lot of sense and I thank you for your reply.

The problem is, the person who the database is for has come up with all
these eventualities that have to be planned for. For instance part of my
database is a phone log system, a call is entered into the database and then
goes to the person's inbox for whom the call was intended. But if that person
wants to send that call onto another person, then I have to run a requery on
the field which might be changed, but then to make sure that the person who
the call has been redirected receives, I have to requery every single
person's inbox so that the call appears there without them having to close
and re-open.

Since I have no idea how your tables or forms are structured, or what
an "inbox" might be in this context, I really can't say.

If it is *necessary* to requery, then you must requery. For many
things, it's not - you can Refresh a form (much cheaper) to see new
edits to records performed by other users, for instance.


John W. Vinson[MVP]
 
Hi John, when I refer to a person's inbox, what I mean is a form with a query
applied to it that filters out all calls that were only intended for them and
aren't marked as complete.

MY boss keeps comign up with all these scenarios that need to be planned
for. And the one that's causing most grief at the moment is what happens when
someone needs to transfer a call toa nother person.

Each call has a field called For which contains a list of all our employees,
each person has their own form which sorts their calls based on this For
frield.

So in a person's inbox, I have on the updateEvent for the For field a
Me.Requery as well as a requery command for everyone else's inboxes. I have
to requery them all as any one person could transfer a call to anyone else.

This telephone log system is alll part of a larger tabbed menu which
includes a Purchase Order system, an ordering system, a quotation system, a
contacts database and a customer complaints database. So overall on this one
tabbed multi form with lots of other sub forms there are quite a few
requeries here and there. I posted this question as I want to make sure it
will run as smoothly and efficiently as possible.

So
 
Back
Top