2007 database crashing

[razorking]

I am at one of those moments when I want to take a big hammer to this computer and go live in a cave somewhere - forsaking all forms of technology.

I have an Access 2007 database that I have been working on for days. Have spent hours on this thing and it is getting close to the point where I was going to give it to the user. This morning I came in and added a new table, created a new report, changed a few things on a form, and then out of the blue it started crashing. The crashes occur every time I click in a text box on a form. The text box is used to search the contents of a listbox. I have suffered about a dozen of these crashes, and it does happen every time.

The odd part is: first the fact that all was good last night when I went home, and I have not added any new code or anything like that - just a few minor tweaks and additions today. The other odd thing is that I have opened the same database with two other computers and these crashes do not occur. So it seems to be my environment (I guess). My PC is current on Windows/Office updates. I ran the Office Diagnostic thing but it found nothing.

I don't know if I should continue working on the database using a different computer or am I to assume I have serious problem (possibly with some code) in this database that I need to resolve first. I guess in summary I am still contemplating whether the problem is with the databse or my computer (the fact that it seems fine on other computers might be my answer - but not totally sure).

Frustrating thing is I don't know how to find out what is causing the problem. I just get the thing popping up and telling me MS Access has encountered a problem and needs to close. Sorry for the inconvenience (and we apparently cannot assist you in any way shape or form to figure out what the heck is causing it to crash- thank you - have a nice day - the fine folks at Microsoft).

Any thoughts??

 

[boblarson]

1. Before doing anything else, make a copy of it and then

2. Open the copy and go to the VBA window and see if it compiles. If not, fix the errors shown, and then

3. create a new ACCDB file and import everything in (even if it does compile).


Then see if that helps.

Corruption can creep in, in many forms. So, also one way to avoid it is to make sure that you aren't opening your copy you are working on from the network drive. Make a copy and work on it on your desktop machine and then put it back. Lost packets or network disruption can wreak havoc with Access databases.

 

[razorking]

1. Before doing anything else, make a copy of it and then


Corruption can creep in, in many forms. So, also one way to avoid it is to make sure that you aren't opening your copy you are working on from the network drive. Make a copy and work on it on your desktop machine and then put it back. Lost packets or network disruption can wreak havoc with Access databases.

I hear you loud and clear and will give this a try. And yes sometimes I do work on it from a network drive - a practice I will try and eliminate. I suspect your answer may be the correct one but, any thoughts on why it appears to behave normally when used on the other two computers but I get the crashing if used on my machine?? It may not be relevant because regardless it might need the action you prescribe - but it is odd

 

[razorking]

Bob,

Your suggestion seems to have been what was needed. Here is the problem, and I know it sounds stupid of me but...what the heck:

I am not very good at VBA. What I have been able to do is use code examples from various sources to incorporate into my databases. Then I also have a habit of scavenging parts and pieces from my existing databases to create new ones. For this particular database I think I exported some existing forms into the new db to start - so there was code attached to those forms that really did not belong in the new database.

I still have a lot to learn.

Thanks!

 

[boblarson]

No worries, using and reusing objects is what a lot of us do. The trick is to remember when to get rid of extraneous stuff and when to make sure to do other things as well. So, usually doing a compile will help track down some of those things laying about that need to be removed; not always, but sometimes.