Run-time error 2046

[Evans2]

Hi all,

Hoping you can help me with this error message that is driving me nuts.

I'm using a split form and I continue to get this Run-time error 2046 message. The problems seems to be with my DoCmd.RunCommand acCmdRecordsGoToLast code I have in the on load event.

The really strange thing is that the error message only pops up maybe 1 out of 20 times the database is opened. I've tried to find the solution but haven't had any luck because the error is so inconsistent.

Any help would be GREATLY appreciated. Screenshots below.



Thank you,




Evan

[June7]

Has to be a cause. Need to document exact circumstances for each occurrence.

Could try alternative code:

Docmd.GoToRecord acDataForm, "form name", acLast

[Missinglinq]

Or even

DoCmd.GoToRecord , , acLast

I think June7's idea is a good one; to be honest I've never seen or heard of

acCmdRecordsGoToLast

and some commands have have problems at certain times/situations, even though they should work.

The other possibility, especially given the sometimes it errors, sometimes it doesn't, is that there is corruption afoot.

Linq ;0)>

[June7]

Seems I've read that DoCmd.RunCommand method is supposed to be 'old school' (deprecated), not recommended.

[Evans2]

Thanks so much! This seems to have done the trick (for now).

[Evans2]

Damn! It just happened again. I seems it´s not resolved after all. I´ll keep searching for a solution.

[Evans2]

Thanks Missinglinq. It seems you may be right and there is some kind of corruption going on. I tried trying to recreate the error on an older, unsplit version of my database and the error doesn´t occur. How can I find the cause? A bit desperate to fix this as there are many people using the database.

[Missinglinq]

...It seems you may be right and there is some kind of corruption going on...

...How can I find the cause?

Ouija board? Crystal ball? Gypsy fortuneteller? With a few exceptions, such as corruption of a Control, it is almost impossible to pinpoint the cause of corruption.

The usual first method of attack is to re-create the errant Form. If this would be too onerous a task, create a new, blank database and import all objects from the errant file into the new one. This would be my suggestion, at this point in time.

Linq ;0)>

[ssanfu]

Looks like the VBA project might be starting to corrupt, If you edit the VBA while in single step debug mode, you can cause corruption of the VBA project.
Been there, done that, managed to survive!

If Linq's suggestion doesn't fix the problem, here is the steps I used to recover. Don't wait too long... at some point your dB might not even open.

See post #2 at https://www.accessforums.net/access/...ect-41760.html