Version 11 project file corruption

[Tom Spitzer]

I appear to have a corrupted EA project file.

There is one node in the model which I cannot open. when I try, it presents a Dialogue that says:

An error has occurred loading the requested project.
DAO.Database [ 3159 ]

Not a valid bookmark

... and the node does not expand.

When I try to Find a diagram node within that model node by name, it displays a message indicating

DAO.Recordset [3343]
Unrecognized database format
'path .... filename'

The good news was that after clicking the ok button, the node opened.

What was interesting about this model (perhaps) is that I was stored on a network drive, and I was connected to the drive remotely. EA crashed due to a network error (this happens to me a lot even with older versions, something you might consider fixing). I then reset the network folder to Windows "work offline" mode, and disconnected my VPN to force EA to work with the local copy. I worked on it for a bit, then this error started to appear.

[qwerty]

Try Tools/Data Management/Project Integrity Check and choose the repair option. That will usually fix such issues.

q.

[Tom Spitzer]

Actually "Repair Project File" is the way to go once you get to the point where EA won't even open the file.

The problem with the progressive disclosure menu system is that you don't even know these tools exist until you go in through "Tools->Customize" to find out what's available that is not appearing in your menu configuration.

I was trying "Project -> Model Validation -> Validate selected" which sounds like it should do that same thing but didn't.

At any rate I was able to rebuild the model from an earlier version and recover the old file based on your tip. Thanks.

It would be really nice if EA could tolerate files on network shares with unreliable connectivity. That's not the first time that bit me.

[Geert Bellekens]

It would be really nice if EA could tolerate files on network shares with unreliable connectivity. That's not the first time that bit me.

I'm afraid that is a bit inherent to the technology. You probably shouldn't use .eap files on an network share (.eap == MS Access).
These types of issues can be avoided by
- Using a real DBMS
- Using local .eap files with version control integration.

Geert