Databases Keep Getting 'corrupted'.

[TG_W]

Robeen,



You might actually run into this often with 2010 if you have installed SP1. There is a fix (supposedly) somewhere on the Microsoft website, but I decompile about once every two weeks.

[Robeen]

It happened again this morning.
I think I'm going to try creating Everything from scratch in a new DB.
I'm just happy this is such a small project and there's no rush on it either.
It's just really frustrating.
It opened up again fine when I did the decompile steps . . .

[TG_W]

Here is the thread on Microsoft's technet forum on the corruption issue. You might want to consider removing SP1 before rebuilding from scratch.

http://social.technet.microsoft.com/...1-installation

[Robeen]

Sorry if this is a stupid question.
How do I determine if SP1 is installed?
Is SP1 something that is specifically tied to an Access install - or is it more a Windows deal?

[Robeen]

My Windows XP System Properties | General tab says Service Pack 3.

[ItsMe]

According to the link provided it has to do with Office 2010 SP1 and a DLL file that SP1 updates.

I guess you could go after the DLL described in the link on the Server that holds the BE.

One of the quotes from the link:
As an update, the SP1 problem only appears to affect the ACCDB copies. If I compile my ACCDE without SP1, then distribute to folks using SP1, the ACCDE seems to work fine.

[Rainlover]

The decompile is very useful and usually fixes these problems. But if it doesn't here are some suggestions.

DO NOT Share the Front End
DO NOT Share a Code Library.
DO NOT Copy a Form or Report unless you first, copy and save the code to Word or similar. Then in the properties where is says Has Module changes this to NO. This is where the strange little bits of unused or deleted code can be found or not found as the case may be. The decompile should have fixed this but it does not always do so. With the Module removed you can make copies under different names then copy back from Word the code that you need. Check your events on the properties as some of these may not have been reactivated. (For want of a better word)

Finally test. If all is OK then Compact and Repair and make a copy.

You should have some form of automatic back up so that you can back up every few minutes. Not at the end of the day. I back up at around every 5 minutes using a special database to do that.
You can have a copy if you want.

Finally if all else fails install Access 2003.

[ItsMe]

Then in the properties where is says Has Module changes this to NO. This is where the strange little bits of unused or deleted code can be found or not found as the case may be.

Interesting tidbit of info here. I understand this is to insure you have an absolutely clear and clean module to recreate your sub routines within the VBE and THEN paste the code within the routine. Am I understanding correctly Rainlover?

[Rainlover]

ItsMe

That is basically right.

I found this by accident many years ago as I was having corruption problems. I was getting error messages concerning code that I had deleted. I could not find the code so the only way I could get rid of it was by deleting the module.

Strangely enough I have over a period of time worked a little cleaner. I no longer get these problems. I do advise a decompile/compile when the project is complete. And always do a back up before a compact and repair.

Nothing scientific in what I said and I doubt if I could reproduce the problem. Just personal experience.

[TG_W]

To see what version you have installed, select File > Help > Additional Version and Copyright Information. You can do that in any Office program, and it will be in the very top line.