Auto FE Updater takes too long to connect

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Trauton - 15 Feb 2006 14:39 GMT

Hi,

I tested Tony's Auto FE Updater and it worked just fine (thanks Tony). The
Auto FE Updater and the latest version for the FE are located in a shared
drive.

The issue I found is that every time I click on the shortcut to run the
program it takes anywhere from 30 seconds to 2+ minutes before I get to the
Access screen. And this is in the case where my version is the latest one,
so the program is not copying a newer version to my computer. Since the
program works fine, I don't know why the checking of the version and
launching of Access takes so long.

I am using a 3MB broadband connection to test this so connection speed is
not the issue. My feeling is that perhaps the share drive takes too long to
answer (though that seems too long even for a share drive).

Has anyone else run into this problem before?

Thank you,

Trauton

Reply to this Message

Tony Toews - 15 Feb 2006 17:50 GMT

>The issue I found is that every time I click on the shortcut to run the
>program it takes anywhere from 30 seconds to 2+ minutes before I get to the
>Access screen. And this is in the case where my version is the latest one,
>so the program is not copying a newer version to my computer. Since the
>program works fine, I don't know why the checking of the version and
>launching of Access takes so long.

How long does it take when you just click on the FE on your system?

And how long does it take when you just click directly on the
StartMDB.exe to get the first screen up. That should be right quick.

The only thing that I can think of that would take so long is that I
open the MDB on the server to see what version of Access it is. But,
when I think about it, maybe I should be opening the local version
after I copy it down. I'd have poke about in the code.

>I am using a 3MB broadband connection to test this so connection speed is
>not the issue. My feeling is that perhaps the share drive takes too long to
>answer (though that seems too long even for a share drive).

Well, a 3Mb broadband connection is definitely too slow to run any
kind of Access FE against an Access BE. A SQL Server data store would
likely work reasonably well so long as you did a lot of fine tuning to
ensure you moved a minimum of data down the wire.

Tom Ellison has tried running an ADP over a dialup and stated that
while it was slow it did work.

Tony

Signature

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

Reply to this Message

Trauton - 16 Feb 2006 00:41 GMT

Tony,

Launching the FE from my computer took 5 seconds to open the application.

Clicking on StartMDB.exe located at the share drive, it took 1 mintue to get
to the first screen.

Thanks for your help!

Trauton

> >The issue I found is that every time I click on the shortcut to run the
> >program it takes anywhere from 30 seconds to 2+ minutes before I get to the
[quoted text clipped - 26 lines]
>
> Tony

Reply to this Message

Tony Toews - 16 Feb 2006 18:20 GMT

>Launching the FE from my computer took 5 seconds to open the application.

Reasonable.

>Clicking on StartMDB.exe located at the share drive, it took 1 mintue to get
>to the first screen.

Yowzer. Now that makes no sense at all. It's only a 221 kb .exe.
I mean you should be able to use a network made out of telephone
connections to open that exe faster.

How long does it take to copy the .exe to your computer?

At this point I have no idea as to why your 3mb broadband connection
is so slow. Possibly the bottleneck is anti virus software. Hmm,
maybe your anti virus software on your PC is set to scan server
folders as well. That's all I can think of.

Tony

Signature

Reply to this Message