I have tried to make a distribution cd and the steps are:
I have a 2003 mdb I converted to a 2007 accdb
Go to MS Office button, Access Options, Advanced, editing, confirm, action
queries
In the accdb be sure check mark is cleared.
Make accde file from button on the access header under database Tools
In the accde be sure the check in Access Options for action queried is
still cleared
Publish package by going to MS Office button, Publish, Package and sign
– use my VBA certificate
Package the application by going to MS Office button, Developer, Package
Solution
Burn to CD from destination folder

The result when installed on another computer with the Access 2007 runtime
still has the action query warning.

I am using the 60 day free trial to see if it is a usable path to
distribute my work but so far it doesn't work.

Help please. I assume I have done something wrong but I can't find any
information to tell me what it is.

Dick Dodge <(E-Mail Removed)> wrote:

>The result when installed on another computer with the Access 2007 runtime
>still has the action query warning.

I prefer, if DAO, to use Currentdb.Execute strSQL,dbfailonerror
command instead of docmd.runsql. For ADO use
CurrentProject.Connection.Execute strCommand, lngRecordsAffected,
adCmdText

If you're going to use docmd.setwarnings make very sure you put the
True statement in any error handling code as well. Otherwise weird
things may happen later on especially while you are working on the
app. For example you will no longer get the "Do you wish to save your
changes" message if you close an object. This may mean that unwanted
changes, deletions or additions will be saved to your MDB.

Also performance can be significantly different between the two
methods. One posting stated currentdb.execute took two seconds while
docmd.runsql took eight seconds. As always YMMV.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

Since I'm a novice I am using macros, It looks like you have jumped to
visual basic (is this correct?)

Is this doable in a macro?

I'll look up what you suggest in the help information. Thanks

"Tony Toews [MVP]" wrote:

> Dick Dodge <(E-Mail Removed)> wrote:
>
> >The result when installed on another computer with the Access 2007 runtime
> >still has the action query warning.
>
> I prefer, if DAO, to use Currentdb.Execute strSQL,dbfailonerror
> command instead of docmd.runsql. For ADO use
> CurrentProject.Connection.Execute strCommand, lngRecordsAffected,
> adCmdText
>
> If you're going to use docmd.setwarnings make very sure you put the
> True statement in any error handling code as well. Otherwise weird
> things may happen later on especially while you are working on the
> app. For example you will no longer get the "Do you wish to save your
> changes" message if you close an object. This may mean that unwanted
> changes, deletions or additions will be saved to your MDB.
>
> Also performance can be significantly different between the two
> methods. One posting stated currentdb.execute took two seconds while
> docmd.runsql took eight seconds. As always YMMV.
>
> Tony
> --
> Tony Toews, Microsoft Access MVP
> Please respond only in the newsgroups so that others can
> read the entire thread of messages.
> Microsoft Access Links, Hints, Tips & Accounting Systems at
> http://www.granite.ab.ca/accsmstr.htm
> Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
>

Dick Dodge <(E-Mail Removed)> wrote:

>Since I'm a novice I am using macros, It looks like you have jumped to
>visual basic (is this correct?)

Correct.

>Is this doable in a macro?

I think you can use SetWarnings in macros.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/