By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,578 Members | 826 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,578 IT Pros & Developers. It's quick & easy.

Help! The dreaded "You can't carry out this action at the present time"

P: n/a

I am designing an Access 2000 database on a computer running Windows 98.
I have one form with several tabs; all of which have sub forms, some
with a subform on a subform.

For example, on my main Job form I have a tab for PO's to keep track of
all purchase orders pertaining to a specific job. The first subform is
for the PO numbers related to the jobs on the main form and the next
subform is for all of the PO lines for each PO. Everything seemed to be
working fine until I added a command button to the header of the PO
subform to show a report for the specific record. I used an access
macro where the action is Open Report and the Where Condition is

At first, all was fine with this and the following day after added it,
when I click on the command button to view the report, after closing the
report and using cmdbutton record secectors I get the error "you can't
carry out this action at the present time". After this I cannot do
anything. No command buttons respond and after shutting the database
the ldb file is still visable. Sometimes after closing the database
after this error I will get the MSAcess has caused and error blah blah
and will be shut down. From this point on restarting the computer,
repairing and compacting the database etc. does not seem to help. When
I reopen the database the same error will happen if I do the same
sequence of events.

Yesterday was the first day this all happened to me. It happened in the
afternoon and haunted me until I left work. Today when I came in my
database ran perfect and I couldn't force it to make the error. I
clicked several buttons, and acted like a crazy user and it just
wouldn't do it. Now, it is the afternoon again and all is going awry.
Same problem as yesterday. GRRRRRRR!!

Can anyone recommend a solution to this. I have several of my subforms
that work this way, one for PO's, one for Faxes and one for Job
Estimates. I am not even sure that the command buttons are causing the
problem. I would like to get this ironed out before letting users
into the database.

Any help anyone can give would be much appreciated. I have looked all
over the Internet and this seems to be a very pesky Access 2000 problem.
Sorry this was so long winded, I just want to make sure I have included
all of the info necessary for diagnosis.

Posted via
Nov 12 '05 #1
Share this Question
Share on Google+
2 Replies

P: n/a

upon doing some more research, this error seems to happen after Access
has been idle for at least an hour. It happened today and yesterday
after I returned from lunch. Anyone know why.


Posted via
Nov 12 '05 #2

P: n/a

This only happens on my computer and not the other users on the network.
It also happens at random times and not only after the computer is idle.
Any ideas?
Posted via
Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.