"Dirty" has a very specific meaning in Access, that data in a Control on a
Form has been changed... you mean "Corrupted", I suspect.
The best collection of information and links about Access multiuser
performance and avoiding corruption that I know about is at MVP Tony Toews'
site,
http://www.granite.ab.ca/accsmstr.htm. Review some of the information
there, and try some of the suggestions, then follow up here.
If you are using Access 2000, and began to experience problems when you
moved from Win 98SE to Win 2000, that is not unusual. What is the OS on the
server/networked machine where the back-end database resides?
Are you using an Access 2000 database as the front-end, and an Access 2000
database as the back-end? I ask, because MDAC 2.8 would have no effect on
that configuration, provided Access 2000 has all the Service Packs applied.
MDAC 2.8, among other things, is for using Access/Jet back end database with
applications created with other software, such as VB or C++ or VB.NET or C#.
Larry Linson
Microsoft Access MVP
"Arturo" <aa*@bbb.com> wrote in message
news:bm**********@news.flashnet.it...
Hello,
I have developed a multiuser application with Microsoft Access 2000
Premium Edition; the application is separate between code and data, the tables are
connected, the data is big as 800 MBytes, it works on LAN 100Mbit.
Before the application was working on Windows 98SE but now it works on
Windows 2000 Professional SP4 and now often the data database become dirty
then I have to repair; I am using MDAC 2.8 too.
Have somebody some suggestion to solve this big trouble?
Thanks in advance
Arturo