High Network Activity When Making Form Design Changes

[Phil]

Hi All,

I've had a problem for some time now when in form design. If any field on
the form is in a linked table, whenever I make any change (even something as
mundane as re-sizing a text box) the network activity icon in the system
tray shows high activity. During this time the whole thing freezes (can be a
minute or more). Once the network activity stops, it un-freezes and I can
carry on. It seems like Access has to transmit or receive megabytes of data
with the linked table everytime I make tiny changes to the form. If I copy
the linked table to the local database, this doesn't happen. Autocorrect is
always switched off. Any thoughts?

Regards,

Phil.

 

[Larry Linson]

I've had a problem for some time now when
in form design. If any field on the form is in
a linked table, whenever I make any change
(even something as mundane as re-sizing a
text box) the network activity icon in the system
tray shows high activity. During this time the
whole thing freezes (can be a minute or more).
Once the network activity stops, it un-freezes
and I can carry on. It seems like Access has
to transmit or receive megabytes of data
with the linked table everytime I make tiny
changes to the form. If I copy the linked
table to the local database, this doesn't happen.
Autocorrect is always switched off. Any thoughts?

I don't have any comments on the necessity for network activity, except to
say that I keep a development copy of the front-end AND a development copy
of the back-end on my local machine. That would seem to prevent such
"network activity" when making changes. Then, you distribute the updated
application front-end to the users, and they relink to the production
tables.

Larry Linson
Microsoft Access MVP

 

[Albert D.Kallal]

two things will fix this

try both

1) check your default printer. If you printer is a network printer..then as
the form is setup, ms-access has to query the printer parameters (it does
this for both reports layout..and the "print" layout for a form - so, double
check your default printer. Because of this problem, my default printer is
now a local (pdf) printer...and thus eliminate this constant "checking" of
the printer layout.


2) setup a persistent connection. YOU REALLY REALLY need to do this anyway
for when the application runs. However, in design mode, obviously your start
code that opens a connection to the back end can't remain open. So, the
simply solution here is to open any table (that is open any tale that is a
linked table to the back end..and simply miminize it..this will give you a
persistent connection). Now, when you design mode...your delay will be
gone..

By the way...post back as how this worked...since we see this
question/problem lots..and the above will fix it.....