Access runtime-action queries must be confirmed?

[TSanders]

Wize ones:

I created an Access database for a local telco that is split into a front
and back end. I would like to distribute the Access runtime along with the
front end. When I use the front end with the Access runtime, I must confirm
every time an action query runs from VBA. I know that in the full version
of Access, a user can opt to turn off notification every time an action
query runs from VBA. Can this option be exercised using the Access runtime?
Or can I maybe put a VBA module in that will stop the confirmation?

Thank you for reading this.

Tammy

[Trevor Best]

TSanders wrote:

Wize ones:

I created an Access database for a local telco that is split into a front
and back end. I would like to distribute the Access runtime along with the
front end. When I use the front end with the Access runtime, I must confirm
every time an action query runs from VBA. I know that in the full version
of Access, a user can opt to turn off notification every time an action
query runs from VBA. Can this option be exercised using the Access runtime?
Or can I maybe put a VBA module in that will stop the confirmation?

DoCmd.Setwarnings False
DoCmd.Openquery "MyUpdateQuery"
DoCmd.SetWarnings True
--
This sig left intentionally blank

[Tony Toews]

"TSanders" <ta*******@tamanders.net> wrote:

I created an Access database for a local telco that is split into a front
and back end. I would like to distribute the Access runtime along with the
front end. When I use the front end with the Access runtime, I must confirm
every time an action query runs from VBA. I know that in the full version
of Access, a user can opt to turn off notification every time an action
query runs from VBA. Can this option be exercised using the Access runtime?
Or can I maybe put a VBA module in that will stop the confirmation?

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

[Trevor Best]

Tony Toews wrote:

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

I was going to suggest the .Execute method in my post (as I've done so
on many posts that start with this FAQ) but nowadays I find I'm thinking
do they have a reference to DAO? or have they succumbed to using the ADO
reference that MS forced on them at the start. This makes answering
simple queries here a lot longer :-(

--
This sig left intentionally blank

[Tammy Sanders]

Yes, I have a DAO reference and no ADO reference. Too many of the users
didn't have the necessary files for me to use the ADO reference and
getting the files installed proved to be impossible on this particular
network, one suffering from a 900+ user base with only 2 administrators.
Thank you for your replies; I plan to try everything listed here on
Monday. :)

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Albert D. Kallal]

I was going to suggest the .Execute method in my post (as I've done so
on many posts that start with this FAQ) but nowadays I find I'm thinking
do they have a reference to DAO? or have they succumbed to using the ADO
reference that MS forced on them at the start. This makes answering simple
queries here a lot longer :-(

Well, if it makes you more happy, do note that access 2003 now has retuned
the DAO ref by default.

I repeat:

MS listened to the people here, and the many posts that resulted in us
telling users to add the DAO ref. So, guess what? For the brand NEW version
of office 2003, the DAO is now again included as a default ref!!
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com
http://www.members.shaw.ca/AlbertKallal

[Trevor Best]

Albert D. Kallal wrote:

I was going to suggest the .Execute method in my post (as I've done so
on many posts that start with this FAQ) but nowadays I find I'm thinking
do they have a reference to DAO? or have they succumbed to using the ADO
reference that MS forced on them at the start. This makes answering simple
queries here a lot longer :-(

Well, if it makes you more happy, do note that access 2003 now has retuned
the DAO ref by default.

I repeat:

MS listened to the people here, and the many posts that resulted in us
telling users to add the DAO ref. So, guess what? For the brand NEW version
of office 2003, the DAO is now again included as a default ref!!

That does make me happy :-) Although I just looked at it and it also
gives an ADO reference as well so people had better start prefixing
theit objects :-\

--
This sig left intentionally blank

[Rick Brandt]

"Albert D. Kallal" <ka****@msn.com> wrote in message
news:FcRRd.438582$6l.394526@pd7tw2no...

I was going to suggest the .Execute method in my post (as I've done so
on many posts that start with this FAQ) but nowadays I find I'm thinking do
they have a reference to DAO? or have they succumbed to using the ADO
reference that MS forced on them at the start. This makes answering simple
queries here a lot longer :-(

Well, if it makes you more happy, do note that access 2003 now has retuned the
DAO ref by default.

I repeat:

MS listened to the people here, and the many posts that resulted in us telling
users to add the DAO ref. So, guess what? For the brand NEW version of office
2003, the DAO is now again included as a default ref!!

Is a DAO reference even required for the following?

CurrentDB.Execute "SomeQueryOrSQL"

I thought I had seen previous posts that indicated that CurrentDB is still
available without a ref to DAO.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com