Error 2486

[kirkm]

I quite often get this error in something I'm developing...

Run-time error '2486':
You can't carry out this action at the present time.

I can't figure out what's causing it and all I need to click "End' and everything carries on as it should.

Can I trap it out altogether, or otherwise prevent it showing ?

Thanks.

 

[JHB]

Do you have some sample database you could post?

 

[kirkm]

Hi JHB, thanks for replying.
It's a bit too large to expect anyone to look at, and is still evolving.
This error is elusive too, doesn't always happen. I did think it might be me (altering things with code
running etc.) but today that was disproved.

 

[JHB]

If you can't tell exact where and when it happen, then it is difficult to help you - try Googling error 2486 ms access then you get a lot of hints.

 

[Solo712]

I quite often get this error in something I'm developing...

Run-time error '2486':
You can't carry out this action at the present time.

I can't figure out what's causing it and all I need to click "End' and everything carries on as it should.

Can I trap it out altogether, or otherwise prevent it showing ?

Thanks.

This error is one of the 'nasties' which often signify a corruption. It has no real known cause, AFAIK. 2486 often happens when opening a new form (especially a modal pop-up) or a report with a DoCmd. Sometimes, it goes away when you decompile and recompile, sometimes it does not. It's finnicky, you might not see it for a while but then it appears again. You can almost bet on it.

I have never been able to get at the bottom of this one. Usually, when I get hit with it I have to recode the module from scratch. Sorry, I can't give you something more positive.

If the error has no effect on the execution you can flush it out with doing this:

On Error Resume Next
' the line that causes the error
If Err.Number = 2486 Then 
    Err.Clear
Else
    MsgBox Err.Number & " " & Err.Description 
    ' decide what next
End if
On Error GoTo ....

Best,
Jiri

 

[spikepl]

When the focus is not where it needs to be to execute the bit of code, you may get this error.

"Corruption" is the carpet many contributors here use to sweep things under if they themselves have no clue. Beware of "corruption" or "access feature" as purported explanation for anything.

 

[Solo712]

When the focus is not where it needs to be to execute the bit of code, you may get this error.

"Corruption" is the carpet many contributors here use to sweep things under if they themselves have no clue. Beware of "corruption" or "access feature" as purported explanation for anything.

"When the focus is not where it needs to be to execute the bit of code, you may get this error". That's very clever, spike, except it doesn't tell you much, does it now ? The fact of the matter is that you are not giving any intelligent description of the cause of the problem, let alone a useful solution to it. I had got this error in two situations which had nothing to do whatsoever with "focus where it needs to be", or a form being "busy" as I read somewhere. The problem went away when in one case when I removed filters from a DoCmd statement (and supplied them via TempVars), and in the other when I rewrote the sub. In a third case the error popped up during dev work on an application which I had run for several years and had half-a-dozen users in production. They had never seen it in the accde app, and neither did I. So, AFAIAC you aren't showing here much else than your charming personality.


Jiri

 

[The_Doc_Man]

I've seen this error when trying to do something to a control that not only wasn't in focus but further was in a state (due to incorrect/incompatible property states on that control) where I couldn't modify the control contents. Once when I hit this one, it was the FORM that was in the wrong state - because of AllowEdits being false or something like that.

Unfortunately, it is vague because it is a catch-all for "selected object properties ain't right" - and I've said that about Access many times. That product just aint' quite right...

I'll say this: I've seen this error a lot less than I used to because I think Access has added a few more errors that are more specific than the catch-all errors - so they have to use these blanket errors less often.

 

[gemma-the-husky]

this isn't necessarily corruption.

I think it might just be something that is generally not available - eg changing a value on a non-updateable record set - and the message reflects the true state of affairs.

if you add some error trapping you should be able to establish exactly which portion of your app is leading to this problem. Assuming you have a source query, it is definitely worth opening this directly to establish whether it is read only, or not

 

[kirkm]

Thanks everyone, for answers. Next time it happens (and it's quite random and can be days apart) I'll try and find out any more clues... anything concrete I'll post here.