We are discussing the pros and cons of building (disconnected) record sets. Debating if the performance is better with the server.createobject in the asp page every time it is used, or if it is better to build a MakeRS function and place it at the end of the ASP or in an included ASP page.<BR><BR>- One arguement is that if there are several Record Sets on a page it will take extra time for the server to interpret the VB code, each time one builds a RS. <BR><BR>-Therefore the desire to build a MakeRS function and place it at the end of the ASP - The con for this is that it takes time to build and destroy each record set in the funtion. (Typically the connection string is the same so we can take advantage of pooling.) the code for this is at the bottom of this post.<BR><BR>Does anyone have an answer to which method will yeild better performance? What happens if the function is placed in an ASP file that is included on the pages where the MakeRS function is needed?<BR><BR><BR>- Thanks<BR>Jordan<BR><BR>&#039;----- EXAMPLE of CODE ---------<BR>dim objRS, strSQL <BR> strSQL = "select * from tablename"<BR> set objRS = MakeRS ( strSQL , application("UDLPATH"), adOpenForwardOnly ,adLockReadOnly )<BR>&#039; Do Stuff with objRS <BR> set objRS = nothing<BR><BR>&#039;---------------------------<BR>function MakeRS (strSQL, strConnect,CursorType,LockType )<BR> dim objRS<BR> set objRS = server.CreateObject("ADODB.Recordset")<BR> with objRS<BR> .CursorLocation = 3 &#039;client<BR> .CacheSize = 25<BR> .CursorType = CursorType<BR> .LockType = LockType<BR> .ActiveConnection = strConnect<BR> .Open strSQL<BR> .ActiveConnection = nothing<BR> end with<BR> set MakeRS = objRS<BR> set objRS = nothing<BR>end function<BR>&#039;---------END CODE<BR>