SQLChanged called twice in quick succession when a table dragged onto the designer
Just an observation really but SQLChanged seems called twice in quick succession when a table dragged onto the designer. (tested in VB too)
I could store the FormattedSQL each time an check if it has changed and if not don't act upon it if it has not but why is it called twice ?
The bug is fixed. The fix will be available in the next build.