A client is using our app over a LAN.
A VB6 front end accesses a Jet database via DAO.
The database connection is is kept open for the duration. They are getting errors like as though the network is down when it isn't.
If I can explain: Sometimes when there's a dodgy network connection a query will fail giving an error along the lines of "unable to find table A". As soon as the network is up again this instance will resume working properly again.
In this case however what happens is that an instance will go down in the manner described above but if a new instance is started it will behave properly (until after a random period it too hangs) meanwhile the previous instance will keep returning error messages suggestive of a network being down and never resume working properly.
Does anyone have an idea what this could be?
*UPDATE 08 Feb2011 The problem has been resolved *
The cause of this problem was the the computer storing the database had a static IP while the rest had dynamic IPs. The static IP address fell within the range from which the dynaic ones were selected. Eventually a dynamic address was generated identical with the static one and caused the issues described above. Thanks to everyone for their comments