Unresponsive form after sitting for a while

[mafhobb]

I have a split database that's been in use for quite a while by 5-10 people. This is a database that is generally opened in the morning, used throughout the day and closed at night. It might happen however that a user opens the db in the morning, adds some data and then goes back to the "search" page, which is an unbound form for a time (1-2 hours) before performing another search and entering data again.

When this happens (the user is logged in but the database has not been used for a time) the database becomes unresponsive and when the user uses the unbound search form by entering search strings in the textboxes and selecting options in the unbound search form, nothing happens when clicking on the "search" button (which obviously contains the search code), or clicking on any other buttons in the form. In other words, the form does not run any code even though it allows for text entering, checkbox selection and button clicking.

No error messages are displayed on the screen and/or recorded in my error audit table and it seems like the only solution is to close the database alltogether and loggin in again.

I believe that this happens to all users.

What could be causing this? Some kind of computer/network connection issue? Energy saving settings? How can I avoid it?

Thanks

mafhobb

 

[gemma-the-husky]

entering data in a search box is unlikely to be using the backend - so you probably don't get an issue until you try to access the backend tables

I suspect that your connection to the backend (on a server) has lapsed, and this is some sort of server issue.

Try to open a table from the navigator panel, and see what happens.

Do you have network administrators who could investigate this sort of thing?

 

[mafhobb]

I'll talk to the network admins to see if they can look into this. In the past I have not had much luck reliying on them for solutions to these kind of issues, so unfortunately I am not too positive that I'll get anything back.

If I had the table that you mention automatically opened (hidden) in each user's front end, would I get an error if their connection to the backend lapses if/when it lapses? What error would that be? Perhaps doing it this way it would be the ultimate proof that this is what happens, but I do not want to cause a major issue by introducing this test and the error I get must be clearly identifiable.

mafhobb