#%$!#% corruption (A2K 9.0.4402 SR-1)

Topic

New Reply

what am i doing with forms that corrupts an access 2k database?

It’s like one form goes haywire and infects those around it?

Is there any way to recover from this absurd behavior?

And why does it happen in the first place!!!!???? ARGH

Reply | Quote

Replies

Sorry, Peter, but there’s no answer to that question. The only serious forms corruption I’ve seen in Access 2000 happened to me when I had Access XP installed on the same machine. After I uninstalled that and reinstalled Office 2k, the problem disappeared.

Reply | Quote

I’ve seen form corruption in Acc 2K, where the form just wouldn’t open in form view, and when you tried to open it in design view, an error message ( I can’t remember what it was) just popped up and wouldn’t let me get at it. Had to start the form from stratch.

Sorry not much help, but I do have sympathy for you

Reply | Quote

The message is “Error accessing file. Network connection may have been lost.”

How did you delete the corrupt form?

What steps necessary to get bakc to a clean mdb?

If you can remember…

Reply | Quote

I think what I had to do in the end was create an entirely new mdb then import all object apart from the one form that was corrupt.

Reply | Quote

In fact, from memory it was actually a Report rather than a form…but same difference

Reply | Quote

Yeah, that’s what i’ve been doing.

What I want is to know which ones i can import and which ones are infected. There oughta be some kind of tool for this…

Better yet, a2k should work properly.

Reply | Quote

Dunno, thinking on my feet now

How about in the ‘corrupt’ database, create this code

Public Function DisplayCorruptForms ()
Dim frm as Form
Dim db as Database
On Error Resume Next
set db = CurrentDB
For each frm in db.Forms
docmd.openform frm.name
If err.number 0 Then
debug.print frm.name
err.number = 0
Else
DoCmd.Close acForm, frm.name
End If
Next frm
End Function

Run this function and it will display those forms names that can’t be opened in the immediate window.

Reply | Quote

ooooh – i gotta try this *after* dinner

Reply | Quote

Peter:
I’ve gone through exactly, word for word, the same problem as you have. As Jayden suggested one of the few options that you have is to start out with a blank database and import. However, you could also try, if you haven’t already, do a compile from debug mode to see if all of your code is clean. The other way I was able to localize my problem, was to bring in the forms 10 at a time, open one of them in program mode, create an Exit System command button, and then see if the system crashes. It always did on mine until the situation was remedied. If it doesn,t crash, then save that copy of your database under a new name and then bring in the next 10 and keep repeating until you eventually narrow it down to the culprit. Painful beyond belief, but unfortunately, about the only thing that you can do. And then send a bill for your time wasted to Bill Gates.

Reply | Quote

Unfortunately database corruption has been with Access (and others too) since day 1. The suggestions for finding the culprit are about your only recourse at this point. Let me suggest you look for the root cause as well:

• is your network indeed flakey and causing hits to occur?
• Do you have Name Autocorrect turned off?
• Is you database split with data in one and the rest in another – if so you might consider making the front-end a MDE – they go corrupt less often, and also make it READ ONLY at the OS level – then it can’t go corrupt
• If you database is split, then consider putting copies on user PCs, and store only the data on the server
  [/list]We’ve gone through similar situations, and twice had to rebuild really complex forms because of it. When we went to deploying the copy on the workstation and making it READ ONLY all that stopped. (We are using SQL Server as the back-end in most cases so we don’t have corruption issues with the data) Hope this helps.

Reply | Quote

Wendel:
I appreciate your input.
The problems occurred on my Home system with only 3 networked stations, so it wasn’t a big deal.
Name Autocorrect was turned on. Not sure what the impact would be one way or the other. It can be a handy little tool. Sort of a poor man’s Speed Ferret.
Database is split. As the problems were in the front end, I’m not too sure as to what the impact would be to make it an MDE. I wouldn’t be able to make it such until it was clean anyways.
I do split the the database between machines.

Short Comment to All: I’ve used http://bbs.elementkjournals.com/ for questions and answers, and this is my first couple of days in Woody’s Lounge. Wow!

Reply | Quote

Take a look at my post here on this problem.

Reply | Quote

1. not a network, just a desktop.
2. Naem autocorrect, eh? i’ll give that a shot
3. db is split, but i’m still working on it.
4. cf 1.

How do you folks make a living with this tool?

Reply | Quote

Hi there,

In reference to what you said:

“Is you database split with data in one and the rest in another – if so you might consider making the front-end a MDE – they go corrupt less often, and also make it READ ONLY at the OS level – then it can’t go corrupt”

How does this stop the back-end from going corrupt. I am going to try this solution, but it kind of bugs me I can’t figure out why this will work.

Thanks,
Rob

Reply | Quote

Unfortunately, it won’t stop the back-end from going corrupt, but back-ends go corrupt much less frequently than front-ends, mostly because people have a form or report or whatever open in the front-end when their PC crashes. Back-ends seem to go corrupt mostly when you are in the process of updating a memo field and something breaks.

The advantage of an MDE is that it is always compiled, so the engine isn’t trying to compile and save code while the database is being used. And when you make the front-end READ-ONLY, the engine can’t make any changes to the database, so it doesn’t have a chance to corrupt. Of course you can’t make the table part (back-end) READ-ONLY, as you wouldn’t be able to edit data! Hope that makes some sense.

Reply | Quote

I think I will do it using the binary method. Import the first half. If it works, then the next quarter, then the next eighth etc. maybe a little faster than 10 at a time, but with the small form count i’m using, either way should do the trick.

Reply | Quote

It sounds like you’ve run into the same problem I encountered and posted on here. I had to uninstall Access 2002, but the problem can be caused by any 2002 app that installs a particular version of the vbe6.dll.

Reply | Quote

Veeerrrry interesting.

I installed Frontpage 02 on this machine, and find vba6.dll v 6.3.91.8 in the MSShared – i wonder if that is what is causing the interference?

Reply | Quote

That’s the version that had my Access tied in knots. Visio 2002 is another app that installs it as well. It appears that the problem doesn’t always occur, since I know of people who are running both versions, but when it does, it drives you crazy.

I’m going to keep nagging Microsoft about this until we get a better answer than just “upgrade to 2002”.

Reply | Quote

You might suggest some kind of price reduction for those of us who’ve wasted a few [insert time increment]s being bitten by this bug.

Perhaps you can pass along the address of who to write to at MS?

Reply | Quote

That version of vbe6.dll is installed by Frontpage 02, which requires that dll to work properly. *sigh*

Reply | Quote