ACCESS FEED: Re: [MS_AccessPros] database very slow on network

thank you, Sarah

3. "tables have mostly one primary key" -- what is Data Type and Size?

4. "relationships" -- defining relationships with referential integrity will make things faster, and is good practice. Here is a video to show you how to do that:

Defining Access Relationships with Enforce Referential Integrity
http://www.youtube.com/watch?v=_zxxc9jzWEg

Taking one of the slow forms: How many records are in the table? Instead of a form having all records in the underlying recordset, it is helpful to limit it to just one record -- this can speed things greatly! Then search combos can be used to change the form recordset to whatever is chosen.

~~~

5. you said you're using Access 2003 ... what version of Access was used to initially create the back-end database?

have an awesome day,
crystal

On 7/8/2019 11:25 AM, sarahk [MS_Access_Professionals] wrote:

1) Was already off

2) cabled

3) very simple and very small db as right now just starting to enter, tables have mostly one primary key

4) no and no.??

as far as this being the only application with a back end and the rest running fine becuase they only do word and excel etc: this is on a large network with other business billing applications. This access db is very minor for this company and only 2 users will use it.

The fact that it runs super fast on a local drive makes me think that the problem is some setting on this network.

I have the same database running on other networks and it works well.

Sarah

---In MS_Access_Professionals@yahoogroups.com, strive4peace wrote :

hi Sarah,

1. did turning off AutoCorrect and SubDatasheet on tables in the back-end make any difference?

2. are you using wi-fi or a cabled connection?

3. what is the Data Type and Size of?? Primary Key and Foreign Key fields? (you might have a lot, so let's just start with the tables for one slow form at a time)

4. are Relationships defined? with Referential Integrity?

Trying to help, but it is hard without knowing more about your database and environment. If something is confusing, no problem, we can clarify for you.?? Thanks.

respectfully,
crystal

On 7/7/2019 4:09 PM, crystal strive4peace [MS_Access_Professionals] wrote:

ps again. I'm sure this is frustrating for you, Sarah. Please know we are doing our best to help even though you haven't answered any questions, and this is an Access forum

a couple more things (aside from what has already been mentioned) you can do with the database to make it faster are:

````````````````````````````````````````````````````````````````````````````
Turn off AutoCorrect

Microsoft Access Flaws - Failures caused by Name Auto-Correct, by Allen Browne
http://allenbrowne.com/bug-03.html

if you haven't turned it off, then it is on

in 2007:

1. Click the Microsoft Office Button Button in the upper left corner
2. choose --> Access Options (lower right corner)

in 2010+

1. File ribbon menu
2. Options (near bottom)

~~~

then:

3. Current Database from left sidebar

in Access 2000 - 2003:
1,2,3. from the menu --> Tools >> Options >> General

-----------------------------------
THEN:
4. Under Name AutoCorrect Options:
uncheck --> Perform Name AutoCorrect
5. Compact/Repair
6. then go back and uncheck --> Track Name AutoCorrect info
7. Compact/Repair again

````````````````````````````````````````````````````````````````````````````

once this is done, Set SubDatasheet to None in all tables.

Microsoft Access Flaws - Problem properties by Allen Browne
http://allenbrowne.com/bug-09.html

~crystal

On 7/7/2019 3:31 PM, crystal 8 strive4peace [MS_Access_Professionals] wrote:

cabled connections are much faster than wi-fi

On 7/7/2019 3:27 PM, crystal?? [MS_Access_Professionals] wrote:

hi Sarah,

it makes absolute sense! Access communicates with the back-end whereas other applications like Excel or Word don't usually have back-ends, so they wouldn't be affected by this.

It could be a cable going to YOUR computer that is bad (or other device). Are you on a local area network with cables, or a wide area network without them? It could just also be a bad connection ... maybe something isn't screwed in tight. Or maybe a cable is sharply bent.

And then, again, maybe it is something else -- but cabling and devices in between your computer and where the back-end is would be the first thing to check.

~crystal

On 7/7/2019 2:37 PM, sarahk@... [MS_Access_Professionals] wrote:

Rob, thanks for your offer but my client will not agree for you to remotely connect.

Suggestions about cabling , wifi speed etc don't make sense if this is the only application on the network that is running so slow.

Sarah

---In MS_Access_Professionals@yahoogroups.com, <strive4peace> wrote :

thank you for your input, Rob -- and very generous of you to offer remote assistance. Perhaps if Sarah takes you up on that, you can share back to the group what needed to change? Nice to see you here!

have an awesome day,
crystal

On 7/7/2019 8:43 AM, Rob Koelmans r.koelmans@... [MS_Access_Professionals] wrote:

Oops, some Office or Windows10 mail filters seem to not like a word I just used.

??

Regarding the issue, if it would help (and practically doable), I can ask a specialized co-worker to assist you with teamviewer, anydesk, skype, remote assist atl.

Rob

??

From: MS_Access_Professionals@yahoogroups.com <MS_Access_Professionals@yahoogroups.com>
Sent: zondag 7 juli 2019 15:11
To: MS_Access_Professionals@yahoogroups.com
Subject: RE: [MS_AccessPros] database very slow on network

??

??

It???s difficult te jump in because it???s an exclusion process. You start by checking the settings on both sides (type of cabling (Wifi??), speed settings, full/half duplex, auto negotiate going wrong, rx/tx-buffers settings, optimizations like jumbo packets/ packet size limitations like QoS), DHCP going wrong so traffic awaits time-outs all the time before choosing a secondary path or protocol, then protocol settings (unnecessary protocols like IPX/SPX, NetBEUI/NetBIOS, IPv6 or IPv4). Then address resolving slowness issues (Wins/Windows-DNS. Then traffic storms, faulty switches and network-cards, unconfigured devices on the network, detected/undetected wrong cable-configuring, then fileshare settings, self-referencing network paths in remote desktop, corrupted disk-i/o, overheated components trying to survive in not working cooling, cpu/memory load at both sides, corrupted/outdated malware stuff. It???s complicated.

Rob

??

From: MS_Access_Professionals@yahoogroups.com <MS_Access_Professionals@yahoogroups.com>
Sent: vrijdag 5 juli 2019 23:05
To: MS_Access_Professionals@yahoogroups.com
Subject: Re: [MS_AccessPros] database very slow on network

??

??

hi Sarah,

I see no one else has jumped in. This is not the right forum to be asking about network speed, although some here may happen to know ...

You didn't mention if you are on a local area network or wide area network. A consideration is how much RAM (random access memory) your machine has. Increasing RAM is one of the best things you can do to enhance machine performance, but the problem could be how you are cabled if local area network, the speed of switches and routers between your machine and the machine with the data, and type of cable. Video cards also have memory to process screen images, and this is another way to increase performance.

To see your machine specs:
From Access or any Office product, click "About [Product]" from File, Account, and then System Info...

Sorry I can't be more helpful.

have an awesome day,
crystal

On 7/4/2019 1:05 PM, sarahk [MS_Access_Professionals] wrote:

The path is very short.

??I realize that local is faster, but the network is so slow, every screen takes a few minutes to load that?? I think it most be some setting on this network. I have installed on other networks and its fine.

Read something about 'Opportunistic locking in the windows file sharing layer ....', but its too technical for me.

??

??

Sarah

---In MS_Access_Professionals@yahoogroups.com, strive4peace wrote :

hi Sarah,

Local will always be faster. One thing you can do to enhance performance is to use a short path. Where is the drive physically located in relation to where you are? And do you know the path of the cables?

a couple suggestions to help performance:

Use short primary and foreign keys like AutoNumber/Long Integer as opposed to text fields with big Size

Build indexes on fields that are used for searching

have an awesome day,
crystal

free code you can use in your projects
https://msaccessgurus.com/code.htm

On 7/3/2019 2:08 PM, sarahk@... [MS_Access_Professionals] wrote:

I just installed a new application: MS Access 2003, split. When I run it on a network drive it is extremely slow, but when I run the exact same application on the local drive it is very fast. I had to move the front and back end to the local drive, just moving the front end did not improve the performance. its a small db , less than 3MB for now.

??

What could be the reason?

??

??

All help is appreciated.

??

Thanks??

Sarah