Does setting the FailOnError property to yes mean that the query is actually executed on the server as Access help suggests?
I have a number of delete and update queries and, in order to try and maximise the speed with which they execute, I have set the 'Use transaction' property to no and the 'FailOnError' property to yes for each.
Some of these queries involve quite a lot of data, however I haven't really noticed any improvements since making these changes.
Also, in a split database (assuming the above is correct) do the queries have to be stored on the back end in order to take full advantage of this?
Does anyone know anything about this?
I have a number of delete and update queries and, in order to try and maximise the speed with which they execute, I have set the 'Use transaction' property to no and the 'FailOnError' property to yes for each.
Some of these queries involve quite a lot of data, however I haven't really noticed any improvements since making these changes.
Also, in a split database (assuming the above is correct) do the queries have to be stored on the back end in order to take full advantage of this?
Does anyone know anything about this?
