Alain CHAZOT
New member
- Local time
- Today, 12:39
- Joined
- Mar 7, 2021
- Messages
- 14
Hello everyone,
(sorry, this is a Google translation from French to English)
I developed an Access application which includes a main base of 35 MB and another base of 70 MB for the linked tables.
It runs on about fifteen PCs on a corporate Ethernet network.
Problem: Users complain of frequent disconnections. Access no longer finds linked tables and displays "?" or "#" in place of data with an error message indicating that the network has been lost or disconnected.
A network audit was carried out by a specialized company but it did not reveal anything abnormal.
After having read what is said on this subject on the net, I modified the addressing of the tables which were written with a network letter at the origin (T:\ in this case) to write it "in hard " with an address like \\servername\directory\file
That should have solved the problem.
But no, the problem persists.
Before installing this new database, we used other Access databases built on the same model and on the same network and we did not have these disconnection problems.
So I come to think that the problem is probably not attributable to the network itself but rather to Access.
What reinforces this hypothesis is also that only Access poses a problem. No worries with the other tools in the Office pack, or with others for that matter.
Have you ever had this type of problem?
Do you know where this problem can come from and how to fix it?
Thank you very much for your precious help.
Alain
(sorry, this is a Google translation from French to English)
I developed an Access application which includes a main base of 35 MB and another base of 70 MB for the linked tables.
It runs on about fifteen PCs on a corporate Ethernet network.
Problem: Users complain of frequent disconnections. Access no longer finds linked tables and displays "?" or "#" in place of data with an error message indicating that the network has been lost or disconnected.
A network audit was carried out by a specialized company but it did not reveal anything abnormal.
After having read what is said on this subject on the net, I modified the addressing of the tables which were written with a network letter at the origin (T:\ in this case) to write it "in hard " with an address like \\servername\directory\file
That should have solved the problem.
But no, the problem persists.
Before installing this new database, we used other Access databases built on the same model and on the same network and we did not have these disconnection problems.
So I come to think that the problem is probably not attributable to the network itself but rather to Access.
What reinforces this hypothesis is also that only Access poses a problem. No worries with the other tools in the Office pack, or with others for that matter.
Have you ever had this type of problem?
Do you know where this problem can come from and how to fix it?
Thank you very much for your precious help.
Alain