Access97->2003 - database corrupted repeatedly

  • Thread starter Thread starter DigitalVinyl
  • Start date Start date
D

DigitalVinyl

We just converted a A97 access MDB -> A2003. The conversion went very
smooth with almost everything works exactly as it has before. This is
a multi-user app, with a backend with data on a networked drive, and a
client locally on each PC. We also moved from WIn98 to WInXP on all
but the server.

The two major issues are

1) database corruptions. At least once-twice a week the database
crashes and Acccess says it is no longer a vlaid format. We must
compact and repair it. We have actually lost a few records now.
Although I think only in the largest table in the database (Clients).

ANyone know of any differences in 2003 that might cause greater
instability in a multi-user access environment?

2) the second thing which may be related is a list box on the forms,
which is linked to the CLIENT Table's key (client ID). Normally this
is in ascending order. However after any use by the clients, it
reorders itself. There is probably some field that is alphabetized but
I haven't spotted yet. If I open the table it is in order. But the
clients listbox is reordered in what looks haphazard, but is actually
a specific ordering sequence because it ALWAYS ends with the same
customers.


Anyone know of defaults that changed moving to 2003? None of us saw
this on tests with 2002--but the tests were not in a full multi-user
network environment.

DiGiTAL_ViNYL (no email)
 
Actually going through the old posts I found reference to a page that
describes OpLock issues when introducing WIN NT/2K/Xp into a Win98
environment. This is the exact situation (file server is just a WIN98
station, but all client have gone to XP. Server will be replaced in
coming months with Server 2003). This looks like a liekly cause... I
won't know till next week for sure.

I also found a note on Norton Antivirus causing OLE errors. Another
problem solved.

The second issue is still open.

DigitalVinyl said:
We just converted a A97 access MDB -> A2003. The conversion went very
smooth with almost everything works exactly as it has before. This is
a multi-user app, with a backend with data on a networked drive, and a
client locally on each PC. We also moved from WIn98 to WInXP on all
but the server.

The two major issues are

1) database corruptions. At least once-twice a week the database
crashes and Acccess says it is no longer a vlaid format. We must
compact and repair it. We have actually lost a few records now.
Although I think only in the largest table in the database (Clients).

ANyone know of any differences in 2003 that might cause greater
instability in a multi-user access environment?

2) the second thing which may be related is a list box on the forms,
which is linked to the CLIENT Table's key (client ID). Normally this
is in ascending order. However after any use by the clients, it
reorders itself. There is probably some field that is alphabetized but
I haven't spotted yet. If I open the table it is in order. But the
clients listbox is reordered in what looks haphazard, but is actually
a specific ordering sequence because it ALWAYS ends with the same
customers.


Anyone know of defaults that changed moving to 2003? None of us saw
this on tests with 2002--but the tests were not in a full multi-user
network environment.

DiGiTAL_ViNYL (no email)

DiGiTAL_ViNYL (no email)
 
DigitalVinyl said:
Actually going through the old posts I found reference to a page that
describes OpLock issues when introducing WIN NT/2K/Xp into a Win98
environment. This is the exact situation (file server is just a WIN98
station, but all client have gone to XP. Server will be replaced in
coming months with Server 2003). This looks like a liekly cause... I
won't know till next week for sure.

DB corrupted again. Despite turning off OpLocks on all the clients.


DiGiTAL_ViNYL (no email)
 
DigitalVinyl said:
DB corrupted again. Despite turning off OpLocks on all the clients.

It's the server which requires OpLocks to be turned off. What kind
of server? If it is Win 95/98/ME, which is highly unlikely, then
that's your problem.

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
 
Back
Top