Access problem?

Short summary of our problem:

Small company running 6 computers on a network through a router. Everything on network works fine with the exception of our main business application Microsoft Access. We have used Access with no problems for years until recently when we began to experience database destroying crashes. Three of the computers on the network run Windows 98 and three run Windows XP. We stopped three of the computers from using the Access database and the crashes have now stopped. We’d like to get all computers back to using the Access but don’t know where to begin. Here are some of the things that we’ve considered may be contributing or possibly causing the problem.
1) Two of our computers run XP home and one XP Pro and the other three run Windows98. This seems like most obvious but also most expensive problem as it would be difficult to afford to upgrade all to an XP version.
2) This problem was initially noticed after two computers had dual monitors installed. Not sure how this could cause a problem but it was right after they were installed that problems started.
3) All machines are running an older version(Access2000) of the Microsoft Access.


Any ideas on where to begin or what to do are appreciated. Thank you.

 

If Access was open and the display driver caused an issue that halted the system (crashed) then the database could get corrupted. I've seen stuff like this happen with old ATI drivers on laptops and MS Word.

I would start with:
1. Updated all display drivers
2. Making sure all desktops have the save version of JET installed (the ms access driver)
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q239114

My ultimate solution would be to make this app into:
1. A true desktop app running off of a database server
2. or write a front end web app that talks to the access DB.

I vote for a combo of #1 and #2 using a web app front end on a database server.