Question My database keeps crashing, I've tried everything, any ideas?

[CarysW]

As a follow up to my post yesterday (http://www.access-programmers.co.uk/forums/showthread.php?t=173930) I've tried numerous things to no avail.

I've worked out that the problem isn't witht he network and it isn't with the software. There's either a problem with my PC(unlikely) or my database(more likely). I've already run Office diagnostics but this came up with no problems. Does anyone know how I can find out if I have some kind of corrupt data within the database?

I'm using Access 2007 with Windows XP Proffesional.

 

[darbid]

As a follow up to my post yesterday (http://www.access-programmers.co.uk/forums/showthread.php?t=173930) I've tried numerous things to no avail

You are now talking about "crashing" does that mean that you are starting your MDB and getting a message or something??

I start many of my answers with "I am not an expert" but have the experience of asking many questions. Unless you are getting some special error message then you are really doing needle in a haystack stuff.

Decompile is definately worth doing (you can set an MDB to decomile each time it is closed (I have this set as an MDB become huge when tables are made/deleted and updated for eg.) - in fact somewhere I have read (there is for sure a link in the forum somewhere) that people do more than just a decompile for example I find that I first decompile - then open a form and debugg > compile - then save - then Tool>Database utilities>Compact and repair your database. I notice that this repair takes a lot longer than a normal one and the size of my MDB sometime drops a lot.

My MDB is about 17md so a lot smaller than yours. I have noticed that sometimes forms "go on holiday" and just never return the same way (become corrupt) so in my non-expert opinion it is sometimes worthwhile debugging the code of a form that might be causing problems - Here I had problems with a dam OCX control and a debug of the form would always fix this problem. (I stress this is just my non technical opinion)

Finally I have now done the process of opening a brand new MDB and importing all objects from you broken database into the new one. On import I got errors - which helped in finding the problem. The MDB size also was a lot smaller and it might be me dreaming but I felt it then ran faster.

 

[CarysW]

You are now talking about "crashing" does that mean that you are starting your MDB and getting a message or something??

I start many of my answers with "I am not an expert" but have the experience of asking many questions. Unless you are getting some special error message then you are really doing needle in a haystack stuff.

Decompile is definately worth doing (you can set an MDB to decomile each time it is closed (I have this set as an MDB become huge when tables are made/deleted and updated for eg.) - in fact somewhere I have read (there is for sure a link in the forum somewhere) that people do more than just a decompile for example I find that I first decompile - then open a form and debugg > compile - then save - then Tool>Database utilities>Compact and repair your database. I notice that this repair takes a lot longer than a normal one and the size of my MDB sometime drops a lot.

My MDB is about 17md so a lot smaller than yours. I have noticed that sometimes forms "go on holiday" and just never return the same way (become corrupt) so in my non-expert opinion it is sometimes worthwhile debugging the code of a form that might be causing problems - Here I had problems with a dam OCX control and a debug of the form would always fix this problem. (I stress this is just my non technical opinion)

Finally I have now done the process of opening a brand new MDB and importing all objects from you broken database into the new one. On import I got errors - which helped in finding the problem. The MDB size also was a lot smaller and it might be me dreaming but I felt it then ran faster.

Sorry, I was being a bit vague with the 'crashing' issue.

Basically, I can open the DB fine but when I try to create a report(usually a one line report) it stops responding and I get a white screen. On the first one or two after I open the DB the system will respond after about 5 mins and the report will open, but usually after I've done a few it just sits there not responding and I have to force it to close.

I've tried compact and repair several times, it doesn't change anything.

I have now just totally reinstalled Access(unistalled and started from scratch).

I've tried opening a new database and working with it and Access works fine.

I'm just trying to import the data into an new database, and Access has stopped responding again.

HELP!

 

[CarysW]

I'm just trying to import the data into an new database, and Access has stopped responding again.

OK so, tried to force Access to close after it stopped whilst importing - clicked on the X on the import box, it came up asking me if I wanted to close Access, I clicked cancel and hey presto there's all of my data! Is Windows/Access having a laugh with me or what?

 

[CarysW]

Have had a look at the error report - it give me the error: 'officelifeboathang'. It would seem it may be a MS problem without a patch. I am running Office 2003 but have Access 2007, this may be the problem so the IT dept are looking for a fix or possible upgrading the whole of my Office suite to 2007! Will keep you posted!

Thanks