Error 2486: Cannot carry out this action at this time

  • Thread starter Thread starter Diarmuid
  • Start date Start date
D

Diarmuid

I have an Orders form. There is a sub form with the Order Lines. The sub
form is based on a snapshot, and is read only. To add a line, the user
clicks a button to open frmPopupOrder. This is bound to the Order Lines
table. When the user closes frmPopupOrder, it returns to frmOrder. However,
if any action is performed, the following error appears
Error 2486: Cannot carry out this action at this time

Application is then locked up, have to close Access.
Using Access 2000 and Windows 2000. Record locking set to Edited Record, and
record-level locking. Split, with back end on server.
There is no problem on my PC, only on the customer site. Happens if only 1
user or many users logged in.
Any ideas?
Diarmuid
 
Hi Diarmuid,

From your descriptions, I understand that you would like to eliminate the
error 2486: Cannot carry out this action at this time.

For better troubleshooting the problems, I've got a few questions regarding
this issue:
1. Was this database application converted from Access 97?
2. Can you determine which line of code that the database stops at when the
error occurs?

There are many previous experience with the same error message, but the
resolution
varies. I've listed all the possible causes and resolutions in the
following:
1. The query that the form ( which shows the detailed information for an
item)
is based on is not done running, when more code is run. You should based
the
form off of a saved query instead of an SQL statement. Also try simplifying
the query a little if it performs complex calculation.

2. There is a reference to a procedure with the name such as
"frmMyForm_Sub".
The form name as it appears in the database window is: "frmMyForm-Sub".
When
using intellisense in Access97, the "-" was converted to "_". Access 2000
doesn't recognize and allow for this apparently.

3. The error was occurring because the query was getting hung up.
Therefore,
any other code that was called after the query was run, would produce the
runtime error. Add some conditional checking in the query using IIF()
function.

4. Particular text box performs some heavy calculation. Delete this text
box.

5. Last resort: re-create the problematic form. There must be some mistakes
with the code that isn't known to us. It may also be corrupt.

Hope this helps and if you have any questions or concerns, don't hesitate
to let me know.

Sincerely yours,

Michael Cheng
Microsoft Online Support
***********************************************************
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks.
 
It wasn't converted from Access 97. No idea which line causes the problem,
it seems to happen after the form closes. I'll try some of your suggestions
below and let you know how I get on.
 
Hi Diarmuid,

I haven't heard back from you yet and I'm just writing in to see if you
have had an opportunity to try my suggestions?

If you could get back to me at your earliest convenience, we will be able
to go ahead. If there was some part of my post that you didn't understand,
please feel free to post here. I look forward to hearing from you.

Thank you for your patience and cooperation.

Sincerely yours,

Michael Cheng
Microsoft Online Support
***********************************************************
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks.
 
Back
Top