469,958 Members | 2,087 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,958 developers. It's quick & easy.

Access 2003 freezes sometimes

344 Expert 100+
I am new to Access 2003 and am running it on Win XP Pro.

Quite often, when I open a database (no startup code) the system freezes. It can take up to 5 mins before I get my cursor back and the database responds.

I get a similar problem saving a form. I have edited 5 forms and then saved them and have had time to leave the office, make a cup of coffee, come back, and it is still saving.

This is happening on 3 different computers, 2 at work, and my own PC at home, all of which have been checked for viruses etc.

Is this normal behaviour for Access 2003 or have I got some option or setting not enabled that should be?

TIA
May 2 '07 #1
8 5625
Denburt
1,356 Expert 1GB
1. Are you saying that this is happening on any and all MS Access databases on these machines or just 1 in particular database?

2. Do your systems meet or exceed the minimum requirements?
http://support.microsoft.com/kb/822129
May 2 '07 #2
Lysander
344 Expert 100+
1. Are you saying that this is happening on any and all MS Access databases on these machines or just 1 in particular database?

2. Do your systems meet or exceed the minimum requirements?
http://support.microsoft.com/kb/822129
I only have 2 databases, the code and the data, and it happening to both of them. Like, just now, I closed the data database (with no code or forms) and after closing, I had the hourglass cursor for about 2 mins before I could open the code dbs.

Yes, the PCs exceed the min requirements.

Not having used Access 2003 before (or Windows XP) I'm not sure if this is normal behaviour or something wrong with our PCs. I've never experienced this with Access 2000 and W2K
May 3 '07 #3
Denburt
1,356 Expert 1GB
There can be a lot of reasons for this...

Have you used compact/repair recently?

Have you added a lot of data recently?

How large are the files?

Have you tried a new database to see what kind of reaction times it has?

Is this on an MDE or MDB file?

I am sure I can think of more give me some time to wake up over here.

BACKUP the database before even thinking about this one, if you create a shortcut then you can use the following in a command line it can resolve some issues.

"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" "C:\YOURDATABASE.MDB" /decompile

Here is one issue it can correct for example:
http://support.microsoft.com/kb/819780
May 3 '07 #4
Lysander
344 Expert 100+
There can be a lot of reasons for this...

Have you used compact/repair recently?

Have you added a lot of data recently?

How large are the files?

Have you tried a new database to see what kind of reaction times it has?

Is this on an MDE or MDB file?

I am sure I can think of more give me some time to wake up over here.

BACKUP the database before even thinking about this one, if you create a shortcut then you can use the following in a command line it can resolve some issues.

"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" "C:\YOURDATABASE.MDB" /decompile

Here is one issue it can correct for example:
http://support.microsoft.com/kb/819780
Thanks for the tips. Both the code and the data are compacted and repaired frequently.

No, not adding any significant data at all yet

Code is 6Mg, data is 18Mg

No, not tried a new database, will do so.

They are both mdb files

Haven't tried the decompile, will do so, and yes, I have many many backups.

One thought, although this may be nonsense. Is it possible for Access 2003 to be set with some sort of CommitChanges flag, and when I quit the database that is what it is doing, commiting all the changes I have made.

The reason I am thinking this is when I started work this morning, the last bit of work I did last night had vanished. I had created a report, run the report, then created a control button on a form for the report, got it all neat, then added some test data (to the data database) and run the report again. In the morning, the report, the button, the code on the form had all vanished. But the test data I created was there. Believe, I spent a long time checking everyone of the backup files and no, I had not created this in one of them.

Like I said, this may all be nonsense but something funny is going on.
May 4 '07 #5
Lysander
344 Expert 100+
Ok, just created a new blank database, imported all the tables from one file, all the other objects from the code file, and quit. Instant response. Went back in, opened all the forms, changed them all and quit. After asking to save, all forms saved and quit almost at once. (In the original system, takes at least a minute to save each form)

Guess this is a problem with my database, not Access. Will try the decompile option in the morning when I am more alert. Thanks for all your help
May 4 '07 #6
Lysander
344 Expert 100+
Ok, just created a new blank database, imported all the tables from one file, all the other objects from the code file, and quit. Instant response. Went back in, opened all the forms, changed them all and quit. After asking to save, all forms saved and quit almost at once. (In the original system, takes at least a minute to save each form)

Guess this is a problem with my database, not Access. Will try the decompile option in the morning when I am more alert. Thanks for all your help

Well, decompile did not solve the problem, still taking several minutes to save a form when I make changes to it. Going to Guinnea-Bissau tomorrow to make system live, so lets hope no performance problems in use.
May 9 '07 #7
Denburt
1,356 Expert 1GB
I hope everything goes well let us know. I have watched MS Access do some strange stuff before, like dropping changes and I have never found a reason for it. There could possibly be a particular program or something conflicting with MS Access or something to that effect. I have to be very careful here because I can design things that run fine on this P.C. but not 1 other P.C. in this office can use it. I know this PC is spiced up a bit but shouldn't have the effects it does on the other P.C.'s. So much of working with MS Access is just trial and error. Good Luck and let us know how it goes.
May 10 '07 #8
Lysander
344 Expert 100+
I hope everything goes well let us know. I have watched MS Access do some strange stuff before, like dropping changes and I have never found a reason for it. There could possibly be a particular program or something conflicting with MS Access or something to that effect. I have to be very careful here because I can design things that run fine on this P.C. but not 1 other P.C. in this office can use it. I know this PC is spiced up a bit but shouldn't have the effects it does on the other P.C.'s. So much of working with MS Access is just trial and error. Good Luck and let us know how it goes.
Well, the system worked fine in Bissau, 7 users, no performance problems (except when they turn the electricity off for 3 hours at lunch time) but still having the same problem of it taking minutes to save a form after I've changed it. Guess its just an Access 2003 thing.
May 29 '07 #9

Post your reply

Sign in to post your reply or Sign up for a free account.

Similar topics

reply views Thread by Mark Reed | last post: by
4 posts views Thread by Jake Jessup | last post: by
reply views Thread by Stumped | last post: by
1 post views Thread by =?Utf-8?B?Q2hyaXM=?= | last post: by
7 posts views Thread by Icarus | last post: by
reply views Thread by rainxy | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.