Constant data corruption with Access 97

[pw]

Hi,

This is only happening to a couple of our clients. We have to have
them e-mail us their data. Then we do a compact and repair and e-mail
it back to them. Then they are fine.

The one that it happens to the most is using our application on a
network.

Is it something we are doing wrong?

We are in the process of migrating it to Access 2003. Will that help?

Thanks,
-pw
remove astericks (*) from e-mail address
(use paulwilliamson at spamcop dot net)

[jer]

I suspect that upgrading to Access 2003 will help. I used to do phone
support for a sofware package writting in an older version of Access.
It was not uncommon for client databases to become corrupted,
expecially on older computers with memory and storage issues. I have
not seen the corruption issues with newer versions of Access.

[Tony Toews]

pw <***paulwilliamson@***spamcop.net> wrote:

This is only happening to a couple of our clients. We have to have
them e-mail us their data. Then we do a compact and repair and e-mail
it back to them. Then they are fine.

The one that it happens to the most is using our application on a
network.
Makes sense.
Is it something we are doing wrong?
Very doubtful. Trouble is there are a lot of things to check.

For more information on corruption including possible causes, determining the
offending PC, retrieving your data, links, official MS KB articles and a list of
vendors who state they can fix corruption see the Microsoft Access Corruption FAQ at
http://www.granite.ab.ca/access/corruptmdbs.htm
We are in the process of migrating it to Access 2003. Will that help?

Very unlikely.

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

[pw]

>I suspect that upgrading to Access 2003 will help. I used to do phone

support for a sofware package writting in an older version of Access.
It was not uncommon for client databases to become corrupted,
expecially on older computers with memory and storage issues. I have
not seen the corruption issues with newer versions of Access.

Good News! Thanks!
-pw
remove astericks (*) from e-mail address
(use paulwilliamson at spamcop dot net)

[pw]

>pw <***paulwilliamson@***spamcop.net> wrote:

This is only happening to a couple of our clients. We have to have
them e-mail us their data. Then we do a compact and repair and e-mail
it back to them. Then they are fine.

The one that it happens to the most is using our application on a
network.

Makes sense.

Is it something we are doing wrong?

Very doubtful. Trouble is there are a lot of things to check.

For more information on corruption including possible causes, determining the
offending PC, retrieving your data, links, official MS KB articles and a list of
vendors who state they can fix corruption see the Microsoft Access Corruption FAQ at
http://www.granite.ab.ca/access/corruptmdbs.htm

We are in the process of migrating it to Access 2003. Will that help?

Very unlikely.

Tony

Thanks again Tony.

We already got out A97 app up and running in A2003. But maybe I
should bite the bullet and rewrite it in Visual FoxPro!
-pw
remove astericks (*) from e-mail address
(use paulwilliamson at spamcop dot net)

[Albert D. Kallal]

"pw" <***paulwilliamson@***spamcop.net> wrote in message
news:3v********************************@4ax.com...

Is it something we are doing wrong?
If you are not running a split application, then that should be near the
top of your list. Splitting a datatabase 9 out 10 times fixes the corruption
problems seen on a typical network.

We are in the process of migrating it to Access 2003. Will that help?

Nope, likely the problem is that you have a incorrect setup for acces97, and
if you carry that incorrect setup to a2003...you fix nothing.

Fix your setup, and move to split arrangement, and most of your problems
will likely go away...
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com
http://www.attcanada.net/~kallal.msn

[David W. Fenton]

"jer" <jm*****@moronifeed.com> wrote in
news:11**********************@f14g2000cwb.googlegr oups.com:

I suspect that upgrading to Access 2003 will help. I used to do
phone support for a sofware package writting in an older version
of Access. It was not uncommon for client databases to become
corrupted, expecially on older computers with memory and storage
issues. I have not seen the corruption issues with newer versions
of Access.

What planet do you live on?

Jet 3.5 (i.e., Access 97) was far, far more stable than any version
of Jet 4 has ever been.

Jet 4 has been the most corrupting version of Jet that I've ever
seen in my 9 years of full-time programming in Access.

Keep in mind also that Active Directory takes away some of your
control of the Jet version installed, since it uses Jet, and
therefore, Jet is part of the OS (Win2K, WinXP). This means that OS
service packs can change your Jet version without you knowing it.

This is *not* an issue with Access97, since AD uses Jet 4.

Anyone who is having corruption in A97 has not properly patched
their versions of Access and Jet. Access should be SR2b and Jet
should be SP3. None of that has changed since about 1999.

If you're a "professional" Access programmer using Access97 with
clients and you don't know that, then you are completely
incompetent.

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

[David W. Fenton]

pw <***paulwilliamson@***spamcop.net> wrote in
news:81********************************@4ax.com:

We already got out A97 app up and running in A2003. But maybe I
should bite the bullet and rewrite it in Visual FoxPro!

Why? Are you a complete blithering idiot?

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

[David W. Fenton]

pw <***paulwilliamson@***spamcop.net> wrote in
news:3v********************************@4ax.com:

Is it something we are doing wrong?

If you are selling yourself as a profession Access developer and
don't know all the issues in troubleshooting corruption in Access97
and what versions of Access97 and Jet are stable, then you are
completely incompetent.

And, yes, that constitutes "doing something wrong" -- you're
fraudulently selling yourself as qualified to provide services you
clearly don't have the knowledge to be providing.

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

[pw]

>"pw" <***paulwilliamson@***spamcop.net> wrote in message

news:3v********************************@4ax.com.. .

Is it something we are doing wrong?

If you are not running a split application, then that should be near the
top of your list. Splitting a datatabase 9 out 10 times fixes the corruption
problems seen on a typical network.

We are in the process of migrating it to Access 2003. Will that help?

Nope, likely the problem is that you have a incorrect setup for acces97, and
if you carry that incorrect setup to a2003...you fix nothing.

Fix your setup, and move to split arrangement, and most of your problems
will likely go away...

The code and data are in separate mdbs.

Following links from http://www.granite.ab.ca/access/corruptmdbs.htm
has enlightened us. The hardware one I think answers the question why
this specific computer at a clients keeps corrupting the database on a
daily basis. There are fax machines, cell phones, printers, hubs, an
other things on that list all around that pc. I think we really
opened our client's eyes!! He is going to talk to his hardware guy.
-pw
remove astericks (*) from e-mail address
(use paulwilliamson at spamcop dot net)