A2003 corrupts - 97 didn't

[Dave G]

I have a medium sized application - data is in back end on a NT4 file
server, front end on about 15 workstations. System was Access 97 on
W2000 workstations and worked fine.

Over Xmas upgraded all workstations to XP Pro with SP2 and Office 2003
Pro. Now I have a corruption problem. Users suddenly report very slow
response, or can't find records. I do a repair on the data and then
find a corrupted record in the table causing problems. I then get rid
of the corrupt record. Then I have to recreate the key index because
that gets lost. Then all is well again for a few days. Then it happens
again.

My question is this - has anyone got any idea why this might be
happening, or better still, how to solve it (a long shot, I know) ?

By the way, at some time in the future, I'm planning to move the back
end to MySQL. Would that help ?

I would really appreciate any assistance

Thanks
Dave

[salad]

Dave G @ K2 wrote:

I have a medium sized application - data is in back end on a NT4 file
server, front end on about 15 workstations. System was Access 97 on
W2000 workstations and worked fine.

Over Xmas upgraded all workstations to XP Pro with SP2 and Office 2003
Pro. Now I have a corruption problem. Users suddenly report very slow
response, or can't find records. I do a repair on the data and then
find a corrupted record in the table causing problems. I then get rid
of the corrupt record. Then I have to recreate the key index because
that gets lost. Then all is well again for a few days. Then it happens
again.

My question is this - has anyone got any idea why this might be
happening, or better still, how to solve it (a long shot, I know) ?

By the way, at some time in the future, I'm planning to move the back
end to MySQL. Would that help ?

I would really appreciate any assistance

Thanks
Dave

A bit ironic. You get the newest and greatest and it turns to crap. As
an old manager once told me, a user will take an ugly system that works
over a pretty system that fails.

I would consider your network connections or network cards. Is there a
user that is experiencing problems with other apps? I really doubt the
OS would have anything to do with it. And I doubt that Access would
fall all over itself simply because it got an upgrade. I can imagine
Access might run a tad slower since there'd be more bloat in the newer
version but not so much that you'd cry over it.

Another thing you might want to try, if it isn't hardware related, is to
decompile the app.
C:\MsAccess.Exe C:\Apps\MyApp.M db /Decompile
Once decompiled, compact the database, and then recompile.

You could also try to import the database into a blank database, rename
the old database, then rename the new to the old name.

And if you have a network connection problem, using MySQL will not help.

[Larry Linson]

Well, what you did was move from the "golden setup for Access multiuser" to
something less "golden". It turns out that the defaults in the NT4 OS and
Access 2.0 or Access 97 seemed to be set "just right" for excellent Access
multiuser.

It's certainly possible to have a stable, good-performing system with the
later versions, but it's likely to take a little more "tweaking". The best
collection of information and links for multiuser environment performance
and corruption avoidance that I know about are at Tony Toews' site,
http://www.granite.ab.ca/accsmstr.htm. Take a look, and try some of the
suggestions.

Larry Linson
Microsoft Access MVP

"Dave G @ K2" <da**@k2compute rs.co.uk> wrote in message
news:11******** **************@ g43g2000cwa.goo glegroups.com.. .

I have a medium sized application - data is in back end on a NT4 file
server, front end on about 15 workstations. System was Access 97 on
W2000 workstations and worked fine.

Over Xmas upgraded all workstations to XP Pro with SP2 and Office 2003
Pro. Now I have a corruption problem. Users suddenly report very slow
response, or can't find records. I do a repair on the data and then
find a corrupted record in the table causing problems. I then get rid
of the corrupt record. Then I have to recreate the key index because
that gets lost. Then all is well again for a few days. Then it happens
again.

My question is this - has anyone got any idea why this might be
happening, or better still, how to solve it (a long shot, I know) ?

By the way, at some time in the future, I'm planning to move the back
end to MySQL. Would that help ?

I would really appreciate any assistance

Thanks
Dave

[Keith Wilby]

"Dave G @ K2" <da**@k2compute rs.co.uk> wrote in message
news:11******** **************@ g43g2000cwa.goo glegroups.com.. .

I have a medium sized application - data is in back end on a NT4 file
server, front end on about 15 workstations. System was Access 97 on
W2000 workstations and worked fine.

Over Xmas upgraded all workstations to XP Pro with SP2 and Office 2003
Pro. Now I have a corruption problem.

I would suspect the NT4 server - I have no hard evidence for a conviction
but I have heard on the grapevine here at my place of work that XP client
and NT4 server is not a good mix. We've just been upgraded from NT4 to XP
on both client and server sides and the whole thing went very smoothly for
Access apps.

Keith.
www.keithwilby.com

[Albert D. Kallal]

Hum, you mention that you have the front end on each workstation...

Have you tried placing a mde on each workstation?

I have a number of clients I moved from a97 to a2003. I always distribute a
mde for the front end.

I have had no problems...perf ormance, or speed wise. And, I find a2003
better then both a2000, and a2002.

In fact, a2003 has been flawless for me...really, very first rate...

By the way, at some time in the future, I'm planning to move the back
end to MySQL. Would that help ?

Yes...that would..and ms-access make a great client to server base systems.
Server based systems don't corrupt..and even with bad network
connections...t hey don't damage the files or indexes....
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl************* ****@msn.com
http://www.members.shaw.ca/AlbertKallal