I'm new here, but I've been researching this problem over the Internet for about a week now and haven't found any solutions.
Windows Server 2003 with Gigabit connection to network.
Windows XP SP2 with 100MBit connection to network
Some have Office 2003 SP2 installed
1 Table with 77 columns. 225,000 rows
32 total users: up to 20 concurrent
Database FE and BE info:
FE is on network share G: accessed by a shortcut on each desktop
BE is on a network share G: in a different folder.
FE is about 2MB in size
BE goes up to 800 MB in size
When a user is entering a new record, there is a combobox that provides a "lookup" function for previous entries for that record in the database. The user, if a record is found, would hit "tab" off of the combobox to continue entering the relevant information for the new record. The problem occurs that if the user does NOT use the mouse scroll wheel to change record either up or down by one, and then go back to the new record prior to tabbing off. The database locks and all other users MS Access crash. Not just the database, All other users in that database have Access crash and want to send a crash report to MS. The databases are compacted regularly, and are not corrupt. Shortcuts and permissions are all set correctly to allow full access. Until a user misses the scroll wheel, everything works perfectly. Once a user does that, everyone has to exit (including the user that missed the scroll wheel) before anyone can get back into the database.
There is an error code that is brought up on all of the machines that have Access crash, but I do not have that number currently, however I was unable to find any relevant information on it online when I did have it a few days ago.
I have read that having the FE DBs on the local machines is recommended, That is not possible in this situation because of the nature of the network and user file permissions on local machine. We tried moving to that previously, and the troubles happened in that environment just the same as in the shortcut to network share environment. Because any changes to the mde file must be propagated quickly to all clients, we decided to keep the centralized mde. Made updates and other maintenance easier and quicker with fewer bugs and missed updates.