Toad World® Forums

Automation


#1

Hi,
When pressed ‘send sql to editor form’ exception happened.

System.NullReferenceException
Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
Stack Trace:
w
Quest.Toad.Workflow.Activities.BaseSQLEntryControl.cbeSqlFile_ButtonClick(Object
sender, ButtonPressedEventArgs e)

w

DevExpress.XtraEditors.Repository.RepositoryItemButtonEdit.RaiseButtonClick(ButtonPressedEventArgs
e)
w DevExpress.XtraEditors.ButtonEdit.OnClickButton(EditorButtonObjectInfoArgs
buttonInfo)
w DevExpress.XtraEditors.ButtonEdit.OnMouseUp(MouseEventArgs e)
w System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32
clicks)
w System.Windows.Forms.Control.WndProc(Message& m)
w DevExpress.Utils.Controls.ControlBase.WndProc(Message& m)
w DevExpress.XtraEditors.TextEdit.WndProc(Message& msg)
w System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
w System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
w System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr
wparam, IntPtr lparam)


Butter

int_1.jpeg
int_1.jpeg


#2

Hi Motyl,

This version of Automation that you see in the latest beta is still under
development. Unfortunately, it cannot be finished before Toad for SQL Server 5.5
feature freeze. That is why it was decided that ToadSS 5.5 will contain the
previous version of Automation engine which in particular doesn’t feature
Activity input controls and shouldn’t therefore have all those validation
synchronization issues. If you’re still interested in using Automation in
ToadSS though, feel free to inspect it in the next beta and see if any of the
issues you discovered are there.

But despite the fact that ToadSS 5.5 will contain the previous version of
Automation engine, we’re working on the new version of it and your
comments are very valuable. Do I understand correctly that “Odwołanie do
obiektu nie zostało ustawione na wystąpienie obiektu” means
“Object reference not set to an instance of an object”?

Thanks,

Igor.
int_1.jpeg


#3

Hi Igor,

Hi Motyl,

This version of Automation that you see in the latest beta is still under
development. Unfortunately, it cannot be finished before Toad for SQL Server 5.5
feature freeze. That is why it was decided that ToadSS 5.5 will contain the
previous version of Automation engine which in particular doesn’t feature
Activity input controls and shouldn’t therefore have all those validation
synchronization issues. If you’re still interested in using Automation in
ToadSS though, feel free to inspect it in the next beta and see if any of the
issues you discovered are there.

ok. I will try.
About usability: Microsoft has decided to move SSiS to separate module. These
means, that I have to work in
2 [at least] modules. Taking it back to one module/ application is imho
advantage.

But despite the fact that ToadSS 5.5 will contain the previous version of
Automation engine, we’re working on the new version of it and your
comments are very valuable. Do I understand correctly that “Odwołanie do
obiektu nie zostało ustawione na wystąpienie obiektu” means
“Object reference not set to an instance of an object”?
[…] ,.,__

Yes. I’m always trying to include translation of such error description, but if
I miss one, you can try to translate it
automatically [from polish]


Butter