Don’t Create a Recordset Unless It’s Required

Don’t Create a Recordset Unless It’s Required

When running action queries make sure you add the adExecuteNoRecords option, so that a recordset is not created. You can also use this technique in lookup situations when returning just a single row with one or two fields (ID values for example). In this case a stored procedure and outparameter will be faster. Here is an example:

 Set cmdUpdate=Server.Createobject(ADODB.Command")strsql = "UPDATE Titles SET Price = Price*1.0" & "WHERE Type _= 'Business'"cmdUpdate.ActiveConnection = cmdUpdate.CommandText = cmdUpdate.CommandType = adcmdstoredprocedurecmdUpdate.Execute , , adExecuteNoRecords

This runs the Update command and ensures that no recordset is created.


About Our Editorial Process

At DevX, we’re dedicated to tech entrepreneurship. Our team closely follows industry shifts, new products, AI breakthroughs, technology trends, and funding announcements. Articles undergo thorough editing to ensure accuracy and clarity, reflecting DevX’s style and supporting entrepreneurs in the tech sphere.

See our full editorial policy.

About Our Journalist