If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Query Confirmations still opening
all,
i figure my solution is to turn off warnings, but i wondered if any knew why query confirmations are still happening when the user says the "confirm" in Editing Advanced Options are unchecked: Record changes, Document Deletions, Action Queries. the user is usually offsite and have no direct access to check whether this is actually true. if any knows why the issue is occurring or has a better solution let me know, TIA. |
#2
|
|||
|
|||
Query Confirmations still opening
You need to to use Set Warnings in code or a macro. Below is an example of a
Make Table query. You could do something similar with a macro and a saved query. You SetWarnings to False before doing the query. Then, and this is important, set it back to True afterwards. Public Sub DoSQL() Dim SQL As String DoCmd.SetWarnings False SQL = "SELECT * INTO Backlog FROM ASA " DoCmd.RunSQL SQL DoCmd.SetWarnings True End Sub -- Jerry Whittle, Microsoft Access MVP Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder. "tighe" wrote: all, i figure my solution is to turn off warnings, but i wondered if any knew why query confirmations are still happening when the user says the "confirm" in Editing Advanced Options are unchecked: Record changes, Document Deletions, Action Queries. the user is usually offsite and have no direct access to check whether this is actually true. if any knows why the issue is occurring or has a better solution let me know, TIA. |
#3
|
|||
|
|||
Query Confirmations still opening
On Wed, 3 Feb 2010 07:50:06 -0800, Jerry Whittle
wrote: You need to to use Set Warnings in code or a macro. Below is an example of a Make Table query. You could do something similar with a macro and a saved query. You SetWarnings to False before doing the query. Then, and this is important, set it back to True afterwards. Public Sub DoSQL() Dim SQL As String DoCmd.SetWarnings False SQL = "SELECT * INTO Backlog FROM ASA " DoCmd.RunSQL SQL DoCmd.SetWarnings True End Sub Even better, in my experience, is to avoid the RunSQL method altogether; instead use the Execute method: Dim SQL As String On Error GoTo Proc_Err SQL = "SELECT * INTO Backlog FROM ASA" Application.Execute SQL, dbFailOnError other code Proc_Exit: Exit Sub Proc_Err: handle any errors generated by the query Resume Proc_Exit -- John W. Vinson [MVP] |
Thread Tools | |
Display Modes | |
|
|