MS SQL: delete column with SQL command => Data => Crash

Hi Ansgar,

I faced one more crash with HeidiSQL v 9.4.0.5144 (64 bit) Compiled on 2017-01-04 09:10:23

SERVER: Microsoft SQL 2012

1. the table myHighSchool.Students was "current" (shown in Data) tab;

2. in the Query tab, I executed this: alter table myHighSchool.Students drop column [marks];

3. I'm switching back to Data tab,

4. crash!

attaching the "save bug report" file content

and the screenshot

Thank you for your work!

//P

date/time : 2017-01-10, 18:44:52, 822ms

computer name : XXXXXXXXXXXX

user name : xxxxxxxxxxxxx <xxxxxx>

registered owner : user

operating system : Windows 7 x64 Service Pack 1 build 7601

system language : English

system up time : 5 days 7 hours

program up time : 41 minutes 5 seconds

processors : 8x Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz

physical memory : 8146/16289 MB (free/total)

free disk space : (C:) 114.66 GB

display mode : 2560x1600, 32 bit

process id : $6408

allocated memory : 268.53 MB

largest free block : 8185.00 GB

executable : heidisql.exe

exec. date/time : 2017-01-10 18:03

version : 9.4.0.5144

compiled with : Delphi XE5

madExcept version : 4.0.12

callstack crc : $6832fff3, $a9cacf22, $a9cacf22

exception number : 1

exception class : EArgumentOutOfRangeException

exception message : Argument out of range.

main thread ($81b4):

00a2acd5 heidisql.exe Data.DB {System.Generics.Collections}TList<Data.DB.TField>.GetItem

00a009ab heidisql.exe Data.DB TFields.GetField

00ab3cb7 heidisql.exe dbconnection 6157 +7 TAdoDBQuery.IsNull

00c53db8 heidisql.exe Main 8536 +17 TMainForm.AnyGridPaintText

00903868 heidisql.exe VirtualTrees 33638 +2 TCustomVirtualStringTree.DoPaintText

00902dd8 heidisql.exe VirtualTrees 33420 +5 TCustomVirtualStringTree.CalculateTextWidth

009033cc heidisql.exe VirtualTrees 33545 +26 TCustomVirtualStringTree.DoGetNodeWidth

008f2ec0 heidisql.exe VirtualTrees 26697 +112 TBaseVirtualTree.GetDisplayRect

00c56696 heidisql.exe Main 9015 +28 TMainForm.AutoCalcColWidth

00c3f846 heidisql.exe Main 4996 +174 TMainForm.DataGridBeforePaint

008dff29 heidisql.exe VirtualTrees 19214 +2 TBaseVirtualTree.DoBeforePaint

008f95aa heidisql.exe VirtualTrees 30013 +5 TBaseVirtualTree.PaintTree

008eaa67 heidisql.exe VirtualTrees 23549 +23 TBaseVirtualTree.Paint

006a5666 heidisql.exe Vcl.Controls TCustomControl.PaintWindow

0069c413 heidisql.exe Vcl.Controls TWinControl.PaintHandler

0069d2af heidisql.exe Vcl.Controls TWinControl.WMPaint

006a55f8 heidisql.exe Vcl.Controls TCustomControl.WMPaint

008dc4c1 heidisql.exe VirtualTrees 17412 +8 TBaseVirtualTree.WMPaint

0040cb1e heidisql.exe System TObject.Dispatch

00694ab3 heidisql.exe Vcl.Controls TControl.WndProc

0069c17e heidisql.exe Vcl.Controls TWinControl.WndProc

008ef36e heidisql.exe VirtualTrees 25273 +32 TBaseVirtualTree.WndProc

0069b3ba heidisql.exe Vcl.Controls TWinControl.MainWndProc

005dbcf3 heidisql.exe System.Classes StdWndProc

7789bd21 ntdll.dll KiUserCallbackDispatcher

77646e67 USER32.dll DispatchMessageW

008145cf heidisql.exe Vcl.Forms TApplication.ProcessMessage

00814643 heidisql.exe Vcl.Forms TApplication.HandleMessage

00814b2f heidisql.exe Vcl.Forms TApplication.Run

00c85667 heidisql.exe heidisql 79 +24 initialization

777459bb kernel32.dll BaseThreadInitThunk

after I click "continue", "Data" tab contains only "no data available for this item" message (while there ARE rows, actually)

this doesn't help to re-vitalize the Data tab:

1. clicking refresh button on top;

2. switching to table definition tab (3rd from the left), clicking refresh button on top, switching back to Data tab

3. selecting the database in the tree on the left and clicking refresh button on top;

4. selecting another table in the tree on the left and selecting myHighSchool.Students that caused the crash;

Probably reconnect will help, but I don't want my queries in separate tabs to be closed (all Queries tab used to be forcibly closed after I disconnect => probably tabs should stay...).

So I invoked one more instance of HeidiSQL and started to work with it...

I can see if I can work around that crash in TAdoDBQuery.IsNull. But I have a gutt feeling there will be follow up crashes.