EA Crashing when attempting to connect to reposito

[Cabelas Sparx Admin]

When we attempt to connect to the repository, EA will try to for about 30-40 seconds then crash. No errors are reported. I believe there is some corruption in the repository but to run the Project Intagrity Check, you have to actually be in the project. This poses a problem for us as we can't even get this far. We are using v7.5.849, has anyone experienced this issue before and if so, how did you resolve it? This has completely shut us down as it's our primary repository.

UPDATE:
Well I found the section in the help file that explains how to fix it, (Repair a Project) the problem is that I can't even get into the project to do any of the steps. Anyone have any ideas?

[Geert Bellekens]

Have you tried the MS Access tools to repair the database?

If that doesn't work you'll have to restore your backup. (which I hope you do have :-/)

Geert

[Cabelas Sparx Admin]

"MS Access Tools" ? :-?

I'll be honest in saying I'm not sure what you are referring to, I'm going to guess it has something to do with Microsoft Access. Would you be kind enough to expand on this?

Oh and yes, we do have a backup.  

[Geert Bellekens]

In fact the .eap file is nothing more then an ms access file with another extension. You can open it with ms access, and use the tools for ms access to repair corrupted files.

Geert

[Cabelas Sparx Admin]

I never knew that, that helps alot.

The only problem I have is that I can't even get into the project itself. I try to connect to the repository and when it tries to open the project, it crashes EA so I'm unable to export the project locally to repair it.

We do have a backup of it so I may just import it and overwrite the exiting one.

[RoyC]

When you say "connect to the repository", which repository (DBMS) are you referring to?

You have a .EAP file in an MS Access Repository, but if you are not sure what the MS Access tools are, it sounds as if you might be using a different repository such as MySQL or Oracle.

The Repair a Project procedure is for a .EAP file, not for projects on server-based repositories.

Can you just clarify what database you are using?

[Geert Bellekens]

Ah indeed, if you are working on a real database, that would change things, I assumed by default that you were using an eap file since you didn't specify something else.

If you indeed are using a real database you might want to setup some logging to find out exactly which sql statement (if any) is causing the crash.
Another thing to look at is the dbError.txt in the main application directory. That log file sometimes shows a usefull database error.

Geert