Results 1 to 3 of 3
  1. #1
    2 Star Lounger
    Join Date
    Jul 2003
    Location
    Newtown, Pennsylvania, USA
    Posts
    119
    Thanks
    0
    Thanked 0 Times in 0 Posts

    To clone or not to clone ...

    That is the question I have - I have a form, the record is selected by a combo box. If the record is updated I get an error message if the recordset is set to the clone but not if the plain recordset is used. Why should I use the clone? (I am talking about general principles here, not specific problems with this code as I have found a 'solution' to the problem I was having.)

    Thanks,

    kiwi44

  2. #2
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: To clone or not to clone ...

    It depends on which version of Access you're using and which object model. I personally haven't found much reason for cloning recordsets in ADO, since ADO clones are independent recordsets. In DAO, clones are used primarily to navigate through a recordset so that you don't "lose your place" in the actual recordset while you're searching for another record in the recordsetclone.
    Charlotte

  3. #3
    2 Star Lounger
    Join Date
    Jul 2003
    Location
    Newtown, Pennsylvania, USA
    Posts
    119
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: To clone or not to clone ...

    Thanks - that was what I thought. Always nice to have thoughts confirmed by an expert!

    kiwi44

Posting Permissions

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