Error: cannot open a form whose underlying query contains a user-defined function that attempts to set or get the form’s recordsetclone property

Question

0.00/5 (No votes)

See more:

On one computer (out of 8) running Windows 10 and Office 365 64 bit, have an Access database with an Access back end. After the database has been idle for a while and they come back to the database will get the above error and the application shuts down. The form uses a query with no function and there are no reference to the RecordsetCone property. Has anyone seen this? Have a fix?

What I have tried:

Have replace the database with a backup copy so don't think it is a corrupt database.

Posted 25-Nov-19 4:38am

Charles 14145266

Updated 26-Nov-19 23:16pm

Add a Solution

Comments

CHill60 25-Nov-19 10:58am

We're getting lots of weird errors here today - we believe our problems are attributable to the last Office 365 Security patch released on 12th November which was recently pushed out to out users. We're uninstalling it as advised by MS and FMS
Microsoft Accesss Query is Corrupt (Error 3340)[^]

phil.o 25-Nov-19 11:04am

That would make an awesome solution.

CHill60 25-Nov-19 11:11am

I might post it as such if uninstalling it cures our problems here :-)

OriginalGriff 25-Nov-19 11:40am

I have to admit that uninstalling Access solved a lot of my problems ages ago! :laugh:

CHill60 26-Nov-19 3:38am

ROTFLMAO!!! If only I could :-( I had VB6 installed for longer than was healthy too.
Some large companies can be so short-sighted on these things

Maciej Los 27-Nov-19 4:58am

What is the meaning of "ROTFLMAO"? I'm very interested!

OriginalGriff 27-Nov-19 5:21am

"Rolling On The Floor Laughing My Ass Off":
https://en.wiktionary.org/wiki/ROTFLMAO

Maciej Los 27-Nov-19 5:52am

More expressive than :laugh:

Maciej Los 27-Nov-19 4:57am

Agree.
My definition is bit different and sounds like: using MS Access causes several problems. So, as an opposite: not using it solves all future problems.
:laugh:

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Maciej Los · Answer 1 · 2019-11-26T23:16:00

There might be set of reasons...

I'd start from recovery mentioned by Guru of MS Access - Allen Browne, see: Microsoft Access tips: Recovering from corruption[^]

At this forum[^] was stated: "IT modified my Group Policy, and the problem has been rectified.". So, check it out if it fix an error in your case.

When none of above won't help, this post might be useful: On error resume next stopped working[^] (this post was made based on my experience).

The last - but the most important - note: Stop using MS Access file as a user interface. Rather than it, use WinForms[^] with ADO.NET[^].

Good luck!