Access Runtime action query confirmation messages showing when unchecked in Database.

Question

Hi all,

I am running an Access 2010 based database under 32 bit Access 2010 Runtime deployed to Windows 10 64 Bit computers.

Recently some, not all, of the clients are showing action query confirmation messages. For those not sure what they are it is a very annoying pop up that happens every time your run a query that appends, deletes or otherwise modifies a table.

I have made sure that the database has set the Access Options > Client Settings > Editing > Confirm Record Changes, Document Deletions and Action Queries are not checked.

I have added trusted locations to Computer\HKEY_CURRENT_USER\Software\Wow6432Node\Microsoft\Office\14.0\Access\Security\Trusted Locations in addition to the original Computer\HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Access\Security\Trusted Locations

I have also added values to allow network locations.

Even tried adding the full UNC path to the database location as well as the mapped drive path

Nothing seems to fix it.

Have even tried to copy a version of the front end that doesn't have this problem from another computer and that doesn't fix it either.

Any ideas as I am seeing reports on other forums as well as here that this is neither new problem nor going away any time soon.

Answer 1

Good question, the answer is I didn't set it in the Runtime because you can't.

I assumed that the DB ( I know it is not best practice, trust me I do, but I didn't create it I inherited it) which is not an accdb but an actual copy of the full mdb should therefore take the settings from the server version of the DB which is copied to the clients. The server does have a full copy of Access and that is where I set the option.

Given that logic I assume the question becomes: if it is a client setting on the local machine and Runtime obviously can't set it where is it set and how and why does it work for some not others.

Answer 2

Hi the application basically has a set of buttons the users press to run the query. It's the usual form with a button that runs a query type Access based thing from years back (this one literally is more than 10 years old)

I totally agree with you about the global turning off of warning messages but hands up I didn't write this I inherited it when I took the job.

Previously the queries all ran without showing a warning message and no code has been changed, literally for years, so I have to assume that the global disable used to work. It still does for most users there are literally a small number for whom it now does not. They problem pops up without warning and once it happens it does not go away.

I like the idea of using CurrentDB.Execute but it's a massive job to edit every query call instance in this application hence the reluctance to start this project.

Answer 3

You're right. It is a client setting, not a current Database Setting.

Answer 4

My question would be how did you manage to go to Access > Options in a runtime environment? Because, if you were doing that in your development machine, I think it's a "client" setting, so it's only applicable to that machine.

Answer 5

How do you run those action queries? In VBA, or directly?

The only one of the things you mention that should impact the display of confirmations would be the Client Settings not to confirm Action queries, and that is specific to the accdb, so if your users have an exact copy of YOUR master accdb, that should be effective.

That said, I would be very leery of actually turning off those confirmation setting globally unless all of your VBA is known to be bulletproof. I want warnings when the unexpected happens.

Also, an alternative to using DoCmd.OpenQuery, which invokes the confirmation, is to use this syntax, calling the Execute method of CurrentDB instead:

CurrentDB.Execute "YourQueryNameGoesHere", dbFailOnError

That allows the query to execute with confirmation, but DOES raise an error if something goes wrong. Both are preferable than "all or nothing"