BIG DATABASE OFTEN DIRTY

[Arturo]

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

[Tom van Stiphout]

Re: BIG DATABASE OFTEN DIRTY

On Fri, 10 Oct 2003 16:18:58 +0200, "Arturo" <aaa@bbb.com> wrote:

Data corruption typically is not a function of database size, but of
bad network connection. Access is very sensitive to this. You'll find
many messages on this subject in groups.google.c om

-Tom.

[color=blue]
>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
>
>[/color]

[David W. Fenton]

Re: BIG DATABASE OFTEN DIRTY

aaa@bbb.com (Arturo) wrote in <bm6el6$iiv$1@n ews.flashnet.it >:
[color=blue]
>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?[/color]

If you're using MDAC, then you're not using Access, but Jet.

The problems must surely be with something you're doing in your
application. To minimize the chance of corruptions, you need to
make sure that you put records in an edited state only for the
shortest period necessary. The longer you have records in an edited
state with pending writes, the more chance there is for a
workstation to crash, for a user to shut down Windows on your app,
for a power plug to get pulled or for something wrong with a faulty
NIC to cause the connection to be lost, which will quite often
(though not always) corrupt your database.

In general, this kind of corruption does not lead to data loss. The
most common corruption that does lead to data loss is with Memo
fields. With MDAC you are probably not using bound controls, but if
you are using bound controls, don't use them with Memo fields --
always edit Memos with unbound controls, because that makes them
much more stable.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Larry Linson]

Re: BIG DATABASE OFTEN DIRTY

"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" <aaa@bbb.com> wrote in message
news:bm6el6$iiv $1@news.flashne t.it...[color=blue]
> Hello,
>
> I have developed a multiuser application with Microsoft Access 2000[/color]
Premium[color=blue]
> 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
>
>
>[/color]

[Tony Toews]

Re: BIG DATABASE OFTEN DIRTY

"Arturo" <aaa@bbb.com> wrote:
[color=blue]
>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;[/color]

Assuming the server is a Windows NT 4.0/Win 2000/Win 2003 Server then your problem is
very likely to be OpLocks. See the Corruptions Causes page at my website for more
info and links.

If your server is still a Win 95/98/ME system then that is your problem. MS
specifically recommends against this.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at

http://www.granite.ab.ca/accsmstr.htm

[Lamont Preager]

Re: BIG DATABASE OFTEN DIRTY


"Arturo" <aaa@bbb.com> wrote in message
news:bm6el6$iiv $1@news.flashne t.it...[color=blue]
> Hello,
>
> I have developed a multiuser application with Microsoft Access 2000[/color]
Premium[color=blue]
> 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
>
>[/color]

Visit the official MVP site:

http://www.mvp.org

Lamont Preager (MVP)

[Tony Toews]

Re: BIG DATABASE OFTEN DIRTY

"Lamont Preager" <LaPre@hotmail. com> wrote:
[color=blue]
>Visit the official MVP site:
> http://www.mvp.org
>Lamont Preager (MVP)[/color]

Don P Mellon

That's www.mvps.org/access.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at

http://www.granite.ab.ca/accsmstr.htm