Client/Server app issue on a network. (1 Viewer)

Hello all.
We have been using a client-server MS-Access 2007 application on a ethernet.
We have server DB stored on a central server as a mdb file, and shared as a "shared folder" to the network.
DB Clients are stored on client PCs and they have linked tables to the mdb on the server.

On some particular clients some particular forms seems to get disconnected from the server and stop responding ("?Name", "Name?" is shown in all the fields). If we close the form and open again, brings all the information up again.

This happens only in some clients, not always. It usually happens when the form is opened for some seconds, and this forms has a subform that has a list based on a query.

Can you please throw some light !!!
Best regards

Do you get any error messages?

You have a mdb on a server that has the Tables. Normally called the "Backend" BE.
You have an individual mdb on each user's PC (there own copy) that has the queries, forms etc. This is the FRONT END (FE). Each of these user FE is linked to the BE.
That's the way you have it set up, correct?

I think this is most often referred to as a Multiuser Access database.

I couldn't explain it better. That's exactly what we have.
We don't get any error message. All the field boxes get blank (Actually shows "Name?") and buttons stop responding.
Sometimes it happens in some computers (clients=FE) for months, then others that were fine it starts to happen... So it doesn't happend in all FE computers.
Best regards

Do you have other issues with your network involving other software? I am not a network specialist, but you may have some network issues. Do you have technical personnel who can check the network and/or server for errors?

Here is an excerpt of a question from a member of a different group (there was no response to this).

At just one of my customers, we've recently had the experience where the FE
files have all, at the same time, had one or more table links disconnect
from the BE file, and then all the table links reconnected no more than 15
minutes later. As far as we know, there was no human intervention. A Disk
or Network Error was recorded by the FE in the GlobalErrors table with is in
the BE file, so this table link did not disconnect.



The network setup is a little complex - they use a Storage Area Network
(SAN) with multiple disks, virtual server (VMWare), and Citrix. The system
is 3 - 6 times slower with data intensive activity compared to my other
customers using a LAN and a physical server.


Anyone have any ideas on a cause, what I can monitor, or what I could do?

Click to expand...

Do you deploy persistency. Do you have a table always open?

Simon

Hold on guys!
In order to be more serious with contributors of this post! We have run a more comprehensive test and what seemed to be ramdom, it may not be.
It can be just a programming error!
Sorry for your contributions and as soon as we fix it we will come back to post it.
Best regards,