query prompts in run-time Access 2007

  • Thread starter Thread starter Charles
  • Start date Start date
C

Charles

I have a simple database that I have packaged with the run-time Access 2007
extensions. In the original database I created I have turned on action query
prompts. But after I compiled it and test it on another PC, I am getting the
action query prompts. How do you ensure that when an Access 2007 database
compiles into a run-time version, it keeps this configuration?
 
I meant that I have turned the action query prompts "off" not "on". and yet
the run-time switches that back on again.

In 2007, if you go to the Windows button in the upper left-hand corner, and
then select "access options", and then "advanced", and then under "editing",
go to "confirm". You have three options: "Record changes", "document
deletions", and "action queries".

This option allows the user to turn off or on these prompts when these
particular type of action queries of being utilized such as in a macro. I
have turned off, or "unchecked" the "action queries".

I get no action queries when I execute macros within the original database.
However, after I create a run-time version of the same database and I test
that run-time version on another computer, I am getting prompted everytime
the action queries are run. For some reason, when I use the compile wizard
with developer extensions, this setting is not kept in the resulting run-time
version.

Perhaps that answers you're most intelligent reponse of "huh?"
 
Sorry, a clarification on Friday evening and a long week - I don't get any
action query prompts when I run the original database. However the prompts
come back in the run-time version.
 
I'm sorry, I didn't understand your question and I have only converted a
handful of datafiles and havn't seen this problem. Are you turning off
warnings in the macros. Of course I understand this is only one more dumb
question so I'll check "out" here. You may want to repost in a new thread
with a new question so others will see the corrected version.
 
No idea why that would happen, but if you add this code to a routine that
runs when your appl starts up it should hopefully take care of it:

Application.SetOption "Confirm Action Queries", False

Here's what I do to determine if it's a test or production version - I check
to see if the startup window is on, which it always is in my test DBs and
never is in production. You may need some other way of determining when you
want this done:

If CurrentDb.Properties("StartupShowDBWindow") Then
 
Back
Top