Access Corruption is a Joke

[whyteo]

What is the problem with Access and Corruption? It is SO bad.

In one evening my command button macros open the wrong forms, my main form does not recognise basic field data (#Name?), and some command buttons give me a "Return without GoSub" error - Compact and Repair does not fix this.

I am so furious that weeks of work are unusable using this expensive software.

-This product is completely unusable for real world professional applications.

 

[Uncle Gizmo]

Ah !!!!

You sound very much like a troll. At least in the way you are writing.

If you would like to ask a question then I am sure someone will be able to help you, it would appear to me that the problem may be with you more than with MS Access.

 

[CEH]

Does this ring a bell........ "GIGO"

 

[RocketRod]

Its not the software. While you are developing your app make backup copies daily at a minumum, or more if you as you get significant functionality added (code developed).

 

[gemma-the-husky]

a) return without gosub is programming errors
b) i wouldnt use any macros

 

[whyteo]

Don't know why, but things resolved...

...God only knows, but the same form works perfectly again!? I suppose that's a good thing, but will it go bust again?

 

[Rabbie]

Perhaps I have been fortunate but I have Access applications written over 10 years ago that have worked properly since then although being used on a daily basis. I have not had any problems with corruption. During their life time they have been converted from A97 to A2000 to A2002 without problem. I attribute the lack of problems to several factors such as using a FE/BE set up and regular compact/repairing both FE and BE databases.

It has also helped to have proper validation of all data input into the DB

 

[Pat Hartman]

Whenever Access or any other application for that matter, starts to act funny, shut everything down and hard reboot. This will get rid of any problems caused by memory leaks from Access or other applications. Then open your Access app and compile it. I have discovered that the newer versions of Access throw some strange and totally unrelated errors when there is a compile error. This is something akin to the problems that happen when a reference is "broken" so that is another thing to test.

 

[whyteo]

Problems are back...

The form again gives the #Name? error for some fields - it is corrected if I reselect the Record Source table from
the Data Tab of the Form Properties.
After I redirect the data source it works fine. It continues to work on closing and reopening, but once I compact and repair it relapses into the same error. Same on exiting access and opening the form (I believe exiting automatically compacts and repairs)
I can't do this continously - should I rebuild the form again?
Also if I try to save the form (F12) I get a crash with the Please tell MS about this problem and restart.
This form is very sick.
Thanks for the advice everyone.

 

[Fifty2One]

The form again gives the #Name? error for some fields - it is corrected if I reselect the Record Source table from
the Data Tab of the Form Properties.
After I redirect the data source it works fine. It continues to work on closing and reopening, but once I compact and repair it relapses into the same error. Same on exiting access and opening the form (I believe exiting automatically compacts and repairs)
I can't do this continously - should I rebuild the form again?
Also if I try to save the form (F12) I get a crash with the Please tell MS about this problem and restart.
This form is very sick.
Thanks for the advice everyone.

I think perhaps you need to rewrite the form that is giving you all the trouble. Rewrite it and dont just try to copy and fix it because there must be an underlaying error that you have missed or is buried or some referral to a non existing object.
I have had forms go real sad mad bad on me while developing and I just have to scrap the offending form report query or what ever and rewrite it.

It is annoying when microsoft logic is counter to your own!