Results 1 to 4 of 4

Thread: Anyone ever encounter error # 35614 ("This would introduce a cycle")?

  1. Jul 10th, 2007, 08:59 AM #1
    BruceG
    BruceG is offline

    Thread Starter
    PowerPoster BruceG's Avatar
    Join Date
    May 2000
    Location
    New Jersey (USA)
    Posts
    2,657

    Anyone ever encounter error # 35614 ("This would introduce a cycle")?

    Hello all,
    I had not yet encountered that one before. It can occur on the DragDrop event when implementing drag-drop within a treeview. I have been using drag-drop within a treeview for years and have not had this error reported, but recently a user encountered this. From what I gather, it has something to do with attempting to move a node such that an invalid parent/child relationship would be created, and my code has always guarded against this. I cannot reproduce the user's error.

    Has anyone ever run into this before? A quick fix would be to trap for that error, and the DragDrop event would simply gracefully deny the move, but I was hoping for more insight on the cause.

    I was not able to find much on a web search of the issue. There is some code in this article which shows the trapping of this error, but in my case, I can't see how the conditions would be right for this to occur. (BTW, this article shows how to use a TV within in Access app, and uses OLEDragDrop, whereas I have a standard VB6 app with "plain" (not OLE) DrapDrop).

    Any further insight would be appreciated.

    http://support.microsoft.com/?id=209898
    "It's cold gin time again ..."

    Check out my website here.
    Reply With Quote Reply With Quote
  2. Jul 10th, 2007, 09:53 AM #2
    MartinLiss
    MartinLiss is offline
    Former Admin/Moderator MartinLiss's Avatar
    Join Date
    Sep 1999
    Location
    San Jose, CA
    Posts
    33,431

    Re: Anyone ever encounter error # 35614 ("This would introduce a cycle")?

    Are you sure about that error number?
    Tips, Examples & Tutorials:
    A valuable forum tool • Generate unique TreeView keys • TreeView with "open" and "closed folder" icons • Time code using GetTickCount • How to trap the Tab key • Scroll a form • NumberBox ActiveX control • Color a ListView row • An InputBox form • How to use SaveSetting and GetSetting • A program registration scheme • Spellcheck a Textbox • Resize controls • Open Windows Explorer at Last Visited Path • A Blackjack Game • Count lines of code • Private Message Viewer • Copy/Paste VB Code • Paste VB Code Add-In • Insert Procedure Names Add-In • A calculator for the game of Spider • My review of REALbasic 2008 • VB6 Debug Tutorial • Picture/Video Viewer • VBF Photo Contest Winners


    2009 - 2016
    Reply With Quote Reply With Quote
  3. Jul 10th, 2007, 11:29 AM #3
    BruceG
    BruceG is offline

    Thread Starter
    PowerPoster BruceG's Avatar
    Join Date
    May 2000
    Location
    New Jersey (USA)
    Posts
    2,657

    Re: Anyone ever encounter error # 35614 ("This would introduce a cycle")?

    Yes - that is the error that is trapped in the MS example I linked to, and is the error number reported by the user (with a screen shot so I am sure).
    "It's cold gin time again ..."

    Check out my website here.
    Reply With Quote Reply With Quote
  4. Jul 12th, 2007, 07:22 AM #4
    BruceG
    BruceG is offline

    Thread Starter
    PowerPoster BruceG's Avatar
    Join Date
    May 2000
    Location
    New Jersey (USA)
    Posts
    2,657

    Re: Anyone ever encounter error # 35614 ("This would introduce a cycle")?

    One bump before this goes to the great thread collection in the sky ...
    "It's cold gin time again ..."

    Check out my website here.
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

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

Forum Rules


Click Here to Expand Forum to Full Width