Form Hangs up only on first open on Network

[Ed Finley]

My front end app startup opens a form that connects to a table in the
backend. On our company network, the first time I open the app, the form
hangs up (I think it's in the on open event where it's hanging up). I close
the app and re-open it and all works well. If I put the back end on the
local computer this never happens. Is there a way to make it open more
patiently while waiting on a slow network?
Thanks,
Ed

 

[Sandra Daigle]

Hi Ed,

I would suspect that you have virus scanning software that is checking the
backend file. Try excluding the backend mdb from any virus scanning software
and see what happens.

For other ideas check here:

http://www.granite.ab.ca/access/performancefaq.htm

 

[Ed Finley]

Sandra,
Thanks for the tip. That did speed it up a bit but something else is
happening, it's still hanging up.
Ed

Hi Ed,

I would suspect that you have virus scanning software that is checking the
backend file. Try excluding the backend mdb from any virus scanning software
and see what happens.

For other ideas check here:

http://www.granite.ab.ca/access/performancefaq.htm


--
Sandra Daigle [Microsoft Access MVP]
Please post all replies to the newsgroup.

My front end app startup opens a form that connects to a table in the
backend. On our company network, the first time I open the app, the
form hangs up (I think it's in the on open event where it's hanging
up). I close the app and re-open it and all works well. If I put
the back end on the local computer this never happens. Is there a
way to make it open more patiently while waiting on a slow network?
Thanks,
Ed

 

[Sandra Daigle]

Hi Ed,

Is it hanging such that it never successfully opens or is it just just
taking an extraordinate amout of time? I ask this because we have an
application (not access) which we thought was hanging but which really just
has a painfully long startup time.

Check your virus software again - make sure that if you have client and
server scanning that both have excluded the mdb file.

Try opening a very simple bound form (possibly hidden) before you open the
main form and see what happens. If possible, create this form and bind it
to a table with a minimal number of rows. Keep this table/form open for the
duration of your session. Often on a network it does take time to establish
the first connection to the backend. If your main form is complex, you have
that initial connect time plus the actual time to load the first recordset
etc.

--
Sandra Daigle [Microsoft Access MVP]
Please post all replies to the newsgroup.

Sandra,
Thanks for the tip. That did speed it up a bit but something else is
happening, it's still hanging up.
Ed

Hi Ed,

I would suspect that you have virus scanning software that is
checking the backend file. Try excluding the backend mdb from any
virus scanning software and see what happens.

For other ideas check here:

http://www.granite.ab.ca/access/performancefaq.htm


--
Sandra Daigle [Microsoft Access MVP]
Please post all replies to the newsgroup.

My front end app startup opens a form that connects to a table in
the backend. On our company network, the first time I open the
app, the form hangs up (I think it's in the on open event where
it's hanging up). I close the app and re-open it and all works
well. If I put the back end on the local computer this never
happens. Is there a way to make it open more patiently while
waiting on a slow network? Thanks,
Ed

 

[Ed Finley]

Sandra,
Thanks again for the suggestion. The workaround you suggested of opening
another form worked. I've got my main menu openning and use the timer event
to open another hidden one in 3 seconds. Do I lose performance with a timer
event that does nothing the rest of the time the program is open? Is there
a way to stop the timer?
Ed

Hi Ed,

Is it hanging such that it never successfully opens or is it just just
taking an extraordinate amout of time? I ask this because we have an
application (not access) which we thought was hanging but which really just
has a painfully long startup time.

Check your virus software again - make sure that if you have client and
server scanning that both have excluded the mdb file.

Try opening a very simple bound form (possibly hidden) before you open the
main form and see what happens. If possible, create this form and bind it
to a table with a minimal number of rows. Keep this table/form open for the
duration of your session. Often on a network it does take time to establish
the first connection to the backend. If your main form is complex, you have
that initial connect time plus the actual time to load the first recordset
etc.

--
Sandra Daigle [Microsoft Access MVP]
Please post all replies to the newsgroup.

Sandra,
Thanks for the tip. That did speed it up a bit but something else is
happening, it's still hanging up.
Ed

Hi Ed,

I would suspect that you have virus scanning software that is
checking the backend file. Try excluding the backend mdb from any
virus scanning software and see what happens.

For other ideas check here:

http://www.granite.ab.ca/access/performancefaq.htm


--
Sandra Daigle [Microsoft Access MVP]
Please post all replies to the newsgroup.


Ed Finley wrote:
My front end app startup opens a form that connects to a table in
the backend. On our company network, the first time I open the
app, the form hangs up (I think it's in the on open event where
it's hanging up). I close the app and re-open it and all works
well. If I put the back end on the local computer this never
happens. Is there a way to make it open more patiently while
waiting on a slow network? Thanks,
Ed

 

[Sandra Daigle]

Hi Ed,

Glad you've made some progress. I wouldn't keep a timer event going after it
is no longer needed - to cancel it just set the timerInterval to 0 after the
code runs once:

Me.TimerInterval = 0

--
Sandra Daigle
[Microsoft Access MVP]
For the benefit of others please post all replies to this newsgroup.

Sandra,
Thanks again for the suggestion. The workaround you suggested of opening
another form worked. I've got my main menu openning and use the timer
event to open another hidden one in 3 seconds. Do I lose performance
with a timer event that does nothing the rest of the time the program is
open? Is there a way to stop the timer?
Ed

Hi Ed,

Is it hanging such that it never successfully opens or is it just just
taking an extraordinate amout of time? I ask this because we have an
application (not access) which we thought was hanging but which really
just has a painfully long startup time.

Check your virus software again - make sure that if you have client and
server scanning that both have excluded the mdb file.

Try opening a very simple bound form (possibly hidden) before you open
the main form and see what happens. If possible, create this form and
bind it to a table with a minimal number of rows. Keep this table/form
open for the duration of your session. Often on a network it does take
time to establish the first connection to the backend. If your main form
is complex, you have that initial connect time plus the actual time to
load the first recordset etc.

--
Sandra Daigle [Microsoft Access MVP]
Please post all replies to the newsgroup.

Sandra,
Thanks for the tip. That did speed it up a bit but something else is
happening, it's still hanging up.
Ed
Hi Ed,

I would suspect that you have virus scanning software that is
checking the backend file. Try excluding the backend mdb from any
virus scanning software and see what happens.

For other ideas check here:

http://www.granite.ab.ca/access/performancefaq.htm


--
Sandra Daigle [Microsoft Access MVP]
Please post all replies to the newsgroup.


Ed Finley wrote:
My front end app startup opens a form that connects to a table in
the backend. On our company network, the first time I open the
app, the form hangs up (I think it's in the on open event where
it's hanging up). I close the app and re-open it and all works
well. If I put the back end on the local computer this never
happens. Is there a way to make it open more patiently while
waiting on a slow network? Thanks,
Ed