In search of a good opinion!

  • Thread starter Thread starter Robert
  • Start date Start date
R

Robert

Hi,

I have to get this off my chest. I don't know if I should
leave what I have done the way it is or not.

I have a main form, lets call it FormA with several
controls and a list box which moves the form to the
record that a user clicks on in my listbox.

Also, in FormA, I have a sub form, lets call it sFormB.
In sFormB I have 2 other sub forms one next to each
other, lets call them sFormC and sFormD.

Now, I say I finally got right, with all the
functionality and data required. HA! My only problem is
that when I click on the list box in FormA, comes a
DISCUSTING FLICKER! (Excuse the expression!) on my
listbox and the hourglass comes on atleast 1/4 second
every time.

Is this normal or am I overloading Access with too many
subforms?

Anyone!
Robert.
 
I need to ask a few questions.
even though ther is a disgusting flicker, does it do what
you want it to do?

Do you know how to debug?

If you reply with some code i may be able to find a clue.
 
Just an addition to my last post.

You will not overload access by binding 4 subforms to a
main form.

And it is normal for the hour glass, but not the flicker.

I can only guess that you have some kind of code like ...
docmd.maximize and everytime you change the recordset you
are also running that code and it is re-maximizing an
already maximized form.

That is only a guess. I hope that helps you.
 
4 subforms is not too many, and 1/4 second of recalculation is not a great
deal (esp. on a slower computer). To try to make it more efficient, trace
the dependencies.

Subform controls has LinkMasterFields and LinkChildFields properties. If you
nominate a calculate control in LinkMasterFields, Access cannot load the
appropriate subform records until it has calculated the main form.

Anything involving Conditional Formatting can make a difference.

Any code in Form_Current of any of the forms can affect recalculation.

Any dependency between forms (e.g. of sFormD depends on a value in sFormC)
makes a difference.
 
Back
Top