Strange sluggish behavior in A 2000

A

Alan B.

Hello,

I don't know what happened to my original post. Someone deleted it.

I have an Access database. A 2000 front end of 9.4 MB, and an A 97 back end
of 37 MB. Everything was running fine up to a few days ago. Now it is acting
strange when client is run both under Win 200 Pro and Win XP Pro on two
different computers.
For example, when I open the database front end and then click a button on
my main menu to open one of the forms, the mouse cursor stays an "I" beam
until I click it on a blank space on the form. Then it turns back into the
usual arrow cursor. This seems to happen on all of the forms, not just one
specific one.

One of the functions in my database is for batch emailing. Now when I try to
email, it will send the first email, but not send any more until I minimize
the A 2000 front end, and then it sends out the rest of the emails.

I've decompiled, recompiled and compacted the Front End. And I've repaired
and compacted the back end. I've been at this stuff with Access since Access
2 back in 1992, but I've never run into this kind of behavior before. I
cannot find anything wrong in either the front or back end. However, it's
misbehaving and it's a real pain.

Does anybody have any ideas or had the same experience?

All Office and Access updates were applied a long time ago, and both of
these computers have never had any problems like this.

Here is another symptom: I have an automation function that allows me to
send a single email from an Access form. It then opens the email in Outlook
2000. Sometimes when I click the Send button, the screen freezes, while the
email seems to have actually been sent. When I click the mouse anywhere on
the screen, it unfreezes and changes to the appropriate view of Outlook.

Any ideas?

Regards,
Alan
 
M

MarinaW

Though I'm a relative novice, I've found that compile & compact, and
decompile and recompile do not serve very well to resolve sluggish behavior
in Ac2003 (and, perhaps as well, in Ac2k)
I've found that the only solution that has served me is to start new Db, and
then import all of your Db into it, and then compile it. Then use this New
Db as you used the old one.
Hope this helps.
A43
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top