Frequent Access 2003 corruption that cannot be repaired

[David W. Fenton]

P.S. Have you noticed this thread header?
Frequent Access 2003 corruption that cannot be repaired

And if I recall correctly, it was due to running Access in an
incorrect scenario, with shared front ends.

Secondly, there are plenty of things one can do to completely avoid
any corruption. My clients and I have not had any corruption of any
Access projects this year. The last one was, I believe, last
September, and it wasn't even corrupt, just flagged uncertain
because of a dirty exit by one workstation.

If you do things right, there's no corruption.

So, I can only conclude, if you're having corruption on a regular
basis, you're doing something wrong.

 

[Tony Toews [MVP]]

There are TOO MANY posts either here or in various forums complaining Access
MDB corruption, either code or objects.

<shrug> We're only seeing those one in 10,000 who are having troubles.
The other 9,999 who are happily running Access we never hear from.

Or pick some other number/percentage.

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

 

[Vladimír Cvajniga]

Check this out:
http://www.google.co.uk/search?hl=en&q=MS+Access+database+corruption&meta=



This one too:

http://www.google.co.uk/search?hl=en&q=recover+MS+Access+database&meta=






And remember: Bug will remain a bug even if it appears only once!!! Now it's
some ten years of my experience with MS Access project MDB corruption. Also
check some newsgroups here in news.microsoft.com. I just can't believe that
VB6 compared to Access NEVER corrupts it's files. To me Access is the only
knows application which has such a problem... :-/
I'd really appreciate if Microsoft could make some research on the bug. The
can even make a hard decision that they will no longer store Access projects
to MDBs (I love VB6 ACSII files!!!) and leave it only for MDE. Sounds good
to me! Hope same for you!!!

Vlado

 

[Vladimír Cvajniga]

Oops 1:
.... is the only knows application ...
.... is the only known application ...

Oops 2:
The can even make a hard decision ...
They can even make a hard decision ...

P.S.
I'd prefer EXEs instead MDEs...

 

['69 Camaro]

Check this out:

http://www.google.co.uk/search?hl=en&q=MS+Access+database+corruption&meta=

Criminy! It happens to SQL Server and Oracle databases, too!

http://www.google.co.uk/search?hl=en&q=SQL+Server+database+corruption&btnG=Search&meta=

http://www.google.co.uk/search?hl=en&q=Oracle+database+corruption&btnG=Search&meta=

I'd really appreciate if Microsoft could make some research on the bug.
The can even make a hard decision that they will no longer store Access
projects to MDBs (I love VB6 ACSII files!!!)

With that logic, I suppose Microsoft and Oracle should store their T-SQL,
PL/SQL, and SQL*Plus code in ASCII files for safety, too, to avoid the
rampant corruption in the database files, huh? ;-)

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blog: http://DataDevilDog.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

 

[Vladimír Cvajniga]

No, I don't share my FE MDB's with anybody. I work from home and I don't
open the same project twice (or more times) on the same machine.
It's quite difficult to avoid some mistakes in programming that can lead to
abnormal termination. It may happen sometimes. But recently I'm having
problems on new projects in A2002: I have a project that I work with. In the
evening (or in the morning) before I go to bed I quit the project and Access
normally. Next time when I try to open the project I have the
"circled-bug-problem", see my earlier post in this thread: Feb 28th 2007
11:30. Believe me, the "circled-bug" is really ANNOYING. It gives me an
option to make a backup but when I quit, MS Access automatically re-opens
the project with the same bug.

I hope that de-compile will help...

Vlado

P.S. I've installed A2002 only a few months ago so it's still new to me.
I was programming in A97 since 1997.

 

[Vladimír Cvajniga]

WOW!

Are these bugs or, as some MVPs & MS guys tend to say, programmers'
mistakes?

Vlado

 

[Vladimír Cvajniga]

Or should they better store VB6 to MDB? :O

V.

 

[Tony Toews [MVP]]

Check this out:
http://www.google.co.uk/search?hl=en&q=MS+Access+database+corruption&meta=
http://www.google.co.uk/search?hl=en&q=recover+MS+Access+database&meta=
So.

And remember: Bug will remain a bug even if it appears only once!!! Now it's
some ten years of my experience with MS Access project MDB corruption. Also
check some newsgroups here in news.microsoft.com. I just can't believe that
VB6 compared to Access NEVER corrupts it's files. To me Access is the only
knows application which has such a problem... :-/

What evidence do you have of VB6 not corrupting files?

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

 

[Vladimír Cvajniga]

I have never experienced any corruption on my VB6 ASCII files (bas, frm,
ctl, vbw, vbp...).
No problem with VB...

V.

 

[David W. Fenton]

I hope that de-compile will help...

If you haven't got COMPILE ON DEMAND turned off and aren't regularly
decompiling, then, as I said, you're not doing it right.

 

[David W. Fenton]

P.S.
I'd prefer EXEs instead MDEs...

Then you really don't understand Access at all.

 

[Vladimír Cvajniga]

Do you remember FoxPro? FoxPro was an interpreter. But they were able to
create EXEs.

Vlado

 

[Vladimír Cvajniga]

COMPILE ON DEMAND is ON.

Vlado

If you haven't got COMPILE ON DEMAND turned off and aren't regularly
decompiling, then, as I said, you're not doing it right.

 

[Vladimír Cvajniga]

Are you sure that Czech version of A2002 can't have some special bugs?
Eg. in query/form design I can't select RecordsetType. You may find my post
complaining the bug somewhere at news.microsoft.com. As far as I can
remember there was no respond on that post.

See:
http://img25.imagevenue.com/img.php?image=14902_A2002_RecordsetType_frm_122_34lo.jpg
http://img17.imagevenue.com/img.php?image=14963_A2002_RecordsetType_qry_122_14lo.jpg

To me it seems that translation for those combo-boxes is incorrect. There
may be hundreds bugs like this in Access.

Vlado

 

[Vladimír Cvajniga]

Are you sure that Czech version of A2002 can't have some special bugs?
Eg. in query/form design I can't select RecordsetType. That's why in some
cases I must change RecordsetType form code.
You may find my post complaining the bug somewhere at news.microsoft.com. As
far as I can remember there was no respond on that post.
See:
http://img25.imagevenue.com/img.php?image=14902_A2002_RecordsetType_frm_122_34lo.jpg
http://img17.imagevenue.com/img.php?image=14963_A2002_RecordsetType_qry_122_14lo.jpg

To me it seems that translation for those combo-boxes is incorrect. There
may be hundreds bugs like this in Access.

Vlado

 

[Vladimír Cvajniga]

1) Decompilation is not documented.
2) If Access needs regular decompilation why MS didn't implement that
function in Access?

 

[David W. Fenton]

COMPILE ON DEMAND is ON.

Turn it OFF and you'll have less corruption.

 

[David W. Fenton]

Are you sure that Czech version of A2002 can't have some special
bugs?

No, I'm not at all sure that there aren't special bugs.

Eg. in query/form design I can't select RecordsetType. You may
find my post complaining the bug somewhere at news.microsoft.com.
As far as I can remember there was no respond on that post.

See:
http://img25.imagevenue.com/img.php?image=14902_A2002_RecordsetType
_frm_122_34lo.jpg
http://img17.imagevenue.com/img.php?image=14963_A2002_RecordsetType
_qry_122_14lo.jpg

To me it seems that translation for those combo-boxes is
incorrect. There may be hundreds bugs like this in Access.

While that's definitely a problem, it wouldn't have any effect on
VBA code. I can't see that there's anything language-specific that
*would* make VBA less stable.

 

[David W. Fenton]

Do you remember FoxPro? FoxPro was an interpreter. But they were
able to create EXEs.

Of course I remember.

That you ask this question shows that you truly *don't* understand
Access, nor why there would be no advantage at all to having an EXE.