I'm experiencing a problem where the AutoFE Updater takes up to a
minute to open databases on my Windows 7 home network. Is there
something wrong with my network configuration that would cause this?

It is definitely the AutoFE Updater (on my network) that is causing
the lag. If I open the mde file that the updater has copied to the C
drive, it opens immediately with no problems.

On Tue, 31 Aug 2010 16:12:59 -0700 (PDT), Wayne
<cqdigital (AT) volcanomail (DOT) com> wrote:

Bizarre. How long does it take to navigate around on your server?
How long does it take to copy down the MDE to your PC from the server?
How long does it take to open the first screen of the StartMDB.exe
when you click on it on the server?

There's nothing extraordinary that I do with the network. So this is
rather baffling to me.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/

On Sep 1, 1:21*pm, Tony Toews <tto... (AT) telusplanet (DOT) net> wrote:

Hi Tony. I'm not using a server as such, but rather a Windows 7 home
network. The problem seems to be a function of Windows 7 and isn't a
problem with the AutoFE Updater as such. I noticed the problem a
while back when trying to install software across the home network.
Any exe regardless of how small takes forever to execute. I'm talking
in excess of 30 seconds for a 2 meg exe.

I experimented with the StartMDB.exe file today. If I copy the exe
across the network, the copy takes place virtually instantly as one
would expect with a file of that size. If I try to run StartMDB.exe
across the network it takes about 50 seconds before the GUI presents
itself. This is the same behaviour I'm seeing with software
installation executables.

If I have the database frontend and backend installed on one network
machine and open the frontend mde from another network machine it is
almost instantaneous.

The main problem in regard to Access databases is that it makes them
extremely slow to start when using the Updater.

On Tue, 31 Aug 2010 23:58:03 -0700 (PDT), Wayne
<cqdigital (AT) volcanomail (DOT) com> wrote:

I have the slow EXE opening issue over my XP Home network, I believe
it is a result of AV, fire-wall and router/switch lag, I have learned
to live with it.
You could try isolating from the internet, turning off all
AV/Fire-wall software and see if the speeds it up, I run my spouses
and the guest machines with "Realtime Scanning" active and they are
slower than my development and inventory machines.
Happy Camping. ldpoos (AT) NOPANTS (DOT) juno.com
Remove NOPANTS To reply by direct E-Mail;

2003 Dodge 1500 QC SB Hemi, A/T, Tow Package, 3.92 gears (11 mpg Towing)
2001 Aerolite 21RDB 21ft TT (Scales 2900 dry)

On Tue, 31 Aug 2010 23:58:03 -0700 (PDT), Wayne
<cqdigital (AT) volcanomail (DOT) com> wrote:

The stupid thing is that the startmdb.exe is digitally signed so the
operating system knows if it's been tampered with.

There will be a version coming out in the next few months which
supports a local copy or install of the startmdb.exe. But it won't
be ready for a while.

In the meantime you could experiment with a local copy of the
startmdb.exe and the configuration files creating shortcuts, etc on
the local system. Of course if you want to use a new version of the
utility you will have to manually copy the startmdb.exe. At least
until the version with this comes out.

I should add that this feature will be part of the Enterprise Edition
for which I will require licensing fees. However if you are using
this on a home network for personal use then I have no problem with
giving you a license file with your name in it.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/

On Tue, 31 Aug 2010 23:58:03 -0700 (PDT), Wayne
<cqdigital (AT) volcanomail (DOT) com> wrote:

Hmm, try the option mentioned at
http://www.autofeupdater.com/pages/settings18.htm <shrug> Dunno if
it will help.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/

On Tue, 31 Aug 2010 23:58:03 -0700 (PDT), Wayne
<cqdigital (AT) volcanomail (DOT) com> wrote:

Also I'd suggest finding an appropriate WIndows 7 forum and ask about
this. http://answers.microsoft.com/en-us/w...ult.aspx#tab=2

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/

On Sep 2, 6:17*am, Tony Toews <tto... (AT) telusplanet (DOT) net> wrote:
Thanks Tony. I'll try all the suggestions. Looking forward to the
next version. When I get some time, I'm going to experiment by
temporarily removing the AV from the 2 machines (currently using
Microsoft Security Essentials and Malware Bytes) and seeing if that
makes a difference.

If that gives me no joy, I'm going to set up an old box I have here as
a server and see how it goes running off that.

On Sep 3, 3:12*pm, Wayne <cqdigi... (AT) volcanomail (DOT) com> wrote:

After posting on a couple of forums I've ascertained that other users
are seeing the same behaviour when trying to run.exe files across a
network.

I still haven't been able to pinpoint what's causing this but as
expected, relocating the "StartMDB.exe" file to the C drive of the
local machine and reconfiguring the shortcut to reflect this rectifies
the problem.