Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Database Keeps Crashing

Status
Not open for further replies.
Jan 11, 2001
8
US
Two of my companies databases have consistently crashed over the last couple of weeks. I'm at my wits end. I've done everything I can possibly think of...compact and repair, called Microsoft (they were no help), reformatted some forms that possibly could have been corrupt, created a new database and imported the tables. Am I missing something?

The "main" database is around 354MB and the "second" database is around 16MB wich includes some linked files from the main database and is usually the one that crashes.

Could linking be a problem? I'm grasping for straws right now incase you couldn't tell.

Thank you in advance for any help that may possibly come my way.
 
What do you mean when you say it crashes? Does it give any kind of error message? Can you open it at all or does the crash happen while you are using it? Also, does it crash when you are doing anything in particular? Have you been having any problems with your network? Does it crash on all machines or just on one? Is it even on more than one machine? If you can answer all these questions you could win $200 and a holiday in to Vatican City. LOL Durkin
 
Thank you for responding Durkin. I've been out for a couple of days but I'm sure the databases are still crashing. The message says something like "not a database" and asks if we want to rebuild. This crash is happening with any one of five to eight user's machines. I read another post by newbieninmd that's having a similar problem. Now I'm wondering if it's because some of the machines are using Windows 2000. However, my machine is Windows 98 and the databases corrupt on my machine as well.
 
There is a thing I found that cures a lot of problems.

Go to the local database that is crashing. Design a module. Do tools references. Untick the ones that are ticked. Choose OK. Close the module and the db. Reopen and retick.

When you close and reopen the database all problems miraculously disappear.

If anyone can tell me why it works for me I'd be grateful. I just know that it does work...
 
Zelandakh, I would suspect that it when you remove all references that it deletes the code necessary to perform those references. And since they are the corruption problem, for whatever reason, it deletes the corrupted code with it. Then you put back the references it writes new code which is not corrupted. DougP, MCP

Visit my WEB site to see how Bar-codes can help you be more productive
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top