Results 1 to 2 of 2

Thread: Explanation needed (on open and close recordset)

  1. #1

    Thread Starter
    Addicted Member
    Join Date
    Sep 2001
    Location
    Malaysia
    Posts
    176

    Wink Explanation needed (on open and close recordset)

    is opening and closing the
    ADODB.recordset and
    ADODB.connection

    for every action(a button click that trigger manipulation to the database) is advisable?

    i mean everytime when you want to manipulate or relate to the database , everytime you gotta set up the connection and recordset again and again ..... Wouldn't that slow down the process?


    (opinion)
    Tell me the TRUTH of the TRUTH, Nothing but the TRUTH,
    Thank You!

  2. #2
    Hyperactive Member
    Join Date
    Sep 2001
    Location
    Orlando
    Posts
    392

    Depends.

    For a standard application that deals with the Database all the time, having an open connection is probably the best choice. But if it performs some Database activity only once in a while, it is better to open a connection and free it after you are done.


    Now the case will be very different in the case of a Distributed Application. I guess that is beyond the scope of this discussion.
    Abu Haider
    ____________________________
    100% Data Validation for the MS DataGrid Control. Plus Support for Custom and Foreign Lists, DatePicker and much more...
    The DataGridEnhancer


    I often point to a place where the problem has been discussed, instead of giving you the code that solves it. This is for good, may be you will understand some day...

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width