search function hangs

[dmcdivitt]

I have an issue with users of an access database. They've been using the database with access 2000 in multi-user mode for a long time. Their workstations were updated to windows 7 and access 2010. The application has bound controls on forms. With their new workstations they can only use the default access search feature once or twice with success. Subsequently the search will hang and never return. They must use task manager to close access, load again, and continue. The same problem occurs if only one user is in the database at a time. There is no backend to the application. All is in one MDB file. If the file is copied to desktop and run there is no issue.

Does anyone have an idea what can be done to resolve this? Thanks

 

[jdraw]

Access for multi-user requires split database---BE--FE.
Do some research on splitting the database; 1 BE on shared drive; a copy of FE on each user's PC.

 

[dmcdivitt]

I understand about splitting the database. I mentioned everything is in the same file for a reason, to say it has not been split. I also said it was working well for a long time. This would not help my issue. We are not going to assume responsibility for maintaining the database or change it. I just need to know if anyone has an idea about the search hanging up. Thanks

 

[Poppa Smurf]

It could be a network problem e.g. too much traffic. Ideally you should have a front end on each user's desktop and the back end on the network server. This will reduce the network traffic in opening the database from the server for each user.

Why don't you try splitting the database and see if the problem exists?

 

[dmcdivitt]

I cannot split the application into front end and back end. This particular user group proceeded to do their own thing and had someone create it for them. We will not take responsibility for it.

The same thing happens if only one person is in the application. It still hangs when doing searches. These are windows 7 machines, but the LAN is Novell. I'm thinking there might be a file caching issue.