[AccessD] Speed Issues on network just with Access App

[Gustav Brock]

Hi John

It would be interesting if you could have the option to fire up a 3040 with a clean Windows 10 install, not an update from Windows 7, and check that out. I have nothing but good experiences with Windows 10.

Also, I must say running a 15-user application in Access 2000 is a bit, eh, exotic. Indeed as you can do a straight upsize to Access 2016 just by opening the mdb and run a convert to the accdb format. The changes needed will be minor if you have no fancy coding.

Not a direct answer to your question, I know, just some thoughts.

/gustav

-----Oprindelig meddelelse-----
Fra: AccessD [mailto:accessd-bounces at databaseadvisors.com] På vegne af John Bodin
Sendt: 7. november 2016 02:45
Til: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Emne: Re: [AccessD] Speed Issues on network just with Access App

Darryl/Jim, thanks for replies and suggestions.  Here's the reason I believe the problem is with the jet engine on the local pc's OR a Windows Update, and not the network.

Everything else runs stellar on the network.  Internet Explorer/Chrome no issues.  VOIP phone system, no problem.  Quickbooks w/6 simultaneous users, no problem.  Opening files over network shares, no problem.  I was hoping I'd have the slow network performance on word/excel files over the network as I have seen that multiple times and have been able to change settings on the server to correct.  Unfortunately, works just fine.  All Windows 7 Pro 64 bit with a few older XP boxes which have never and still never experience the speed problem.

I eliminated the new gig switch I put in a little while back by getting an older model that is much less sophisticated, and no issues w/anything except the random slowdowns with Access.  That goes for both the new and the older switch so I have to rule that out.  And rule out the wiring as I have moved workstations around to see if maybe a bad cable was in play, but problem still randomly happens on original location and moved location.

The server does not have Access installed, just has the MDB's on a shared drive.  Copy of FE on local PC's C drive.  I have some C drives that are SSD's, but doesn't seem to matter.

What the norm has been for the 20+ years this A2K system has been around is that if you are the only one in (say on a Saturday), everything is lightning fast.  Screens open in a second or less.  When 2 or more people get in, then the screens slow a bit, but usually no more than 2 seconds to open any form, very acceptable.  No complaints, even when 15+ are in at the same time, some running multiple instances of Access (one instance runs a Dispatch Board on one monitor, the other instances runs the rest of the program, like Work Order Entry, Purchase Orders, Quotes, etc.)  The other thing I always do before putting an update into the FE is to create a blank MDB and import all the objects from the FE I'm working on and compile the FE.  This is what they run, a clean FE. There was phenomenon back on their server in Windows NT days where if I made a change to a report or form say on one machine, which would decompile that FE, if a second person connected to the app, they would no!
 tice a 2 - 3 minute delay in opening any form, every time they clicked on a button or other form.  As soon as everyone got out, one person was left, that person would experience very fast performance again.  Creating blank mdb and importing all objects and compiling took care of this, so I keep doing this slightly pain in the tail procedure whenever making updates to the system.

Finishing up, not too many months ago the speed issue creeped in.  It was around the time of both the addition of the new switch and introduction of Dell 3040 Optiplex Micro machines.  I have addressed removing network switch, but that didn't help.  I can't remove all of the 3040's because of problem with old XP boxes and the version of QB people are running.  There are maybe 4 or 5 3040's in play.  Quite possible a Windows Update came across which would only effect the Win7 boxes, that's a high possibility in my book.

And not being able to explain this one, I've seen a person being the only one in the system on a Saturday morning and the system hung for minutes at a time (white screen) just opening the Access App.  Not even the typical places which are several of the forms/procedures.  That had never happened ever, so a gremlin has snuck in somewhere and I just do not know where.  I do not know what tool(s) to utilize that may help determine the hangup (maybe something like Wireshark, I do not know.)

Thanks for listening.

John