Program crash

This topic is empty.

Viewing 13 reply threads

Author

Posts
- May 23, 2005 at 10:02 pm #9001
  
  sdpippin
  Member
  
  If I run a query, change the drop down bos to allow for copying, highlight a particular value, then run another query yog crashes.
- May 24, 2005 at 3:16 am #17906
  
  Ritesh
  Member
  
  Which version of SQLyog are you using?
  
  I am not able to reproduce error on my side with v4.06.
- May 24, 2005 at 8:12 am #17907
  
  Shadow
  Member
  
  Bug confirmed with v4.06 on W2K!!!!!
  
  Steps to reproduce the error:
  
  -Execute a SELECT statement from SQL window
  
  -Change to updatable resultset in the drop-down combo box
  
  -Highlight the contents of a field
  
  -Execute another SELECT query from SQL window (the highlighted cell remains highlighted!!!!!)
  
  -Left click on the result pane and SQLyog crashes…
  
  Highlighted cell after the first query:
- May 24, 2005 at 8:15 am #17908
  
  Shadow
  Member
  
  Screenshot No. 2. shows SQLyog after execution of 2. SELECT. Note that the value of highlighted cell is still visible!
- May 24, 2005 at 8:18 am #17909
  
  Shadow
  Member
  
  And finally, SQLyog crashed after clicking on the result pane (error message is in Hungarian)…
- May 24, 2005 at 8:40 am #17910
  
  Shadow
  Member
  
  Table data view is not affected by this error.
- May 24, 2005 at 11:56 am #17911
  
  Ritesh
  Member
  
  My testing team has confirmed the bug in W2K. It does not effect Win XP.
  
  We will fix the bug in v4.07.
- May 24, 2005 at 12:07 pm #17912
  
  Shadow
  Member
  
  That damn W2K, right? 😛
- May 24, 2005 at 2:16 pm #17913
  
  sdpippin
  Member
  
  Actually I am getting the problem using Win XP sp2.
- May 24, 2005 at 2:19 pm #17914
  
  peterlaursen
  Participant
  
  @ sdpippin
  
  Has your XP been installed “upon” a win-2K installation then ??
- May 25, 2005 at 8:34 am #17915
  
  Shadow
  Member
  
  Or simply downgraded XP's display to W2K style 😀
- June 1, 2005 at 5:46 pm #17916
  
  sdpippin
  Member
  
  It was installed on top of windows 2000.
- June 1, 2005 at 8:28 pm #17917
  
  peterlaursen
  Participant
  
  Quote:
  
  It was installed on top of windows 2000.
  
  Then I believe the error is the same as with a win2K installation. Registry structure and data are not totally identical with a fresh XP-install as an “op top install”. I might even depend on the SP-level of the 2K of the time you updated.
  
  So the fix for 2K when it is out should probably help you as well.
- June 14, 2005 at 7:50 am #17918
  
  Ritesh
  Member
  
  Bug fixed in v4.07 development tree.
Author

Posts