Unhandled exception

virtking

I got the following exception using the released version:

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at _7._1(UInt64 )
at _7._1(UInt64 )
at RedGate.SQLCompare.Engine.StoredProcedure._1(IBlockWriter , SqlSetOptions , Options , Boolean , String , String )
at RedGate.SQLCompare.Engine.StoredProcedure.ScriptObject(SqlSetOptions sqlSetOptions, Options options)
at RedGate.SQLCompare.Engine.Work.ScriptObject(IDatabaseObject objectToScript, Options options)
at _94._5()
at _94._1(Difference )
at _92._2(Boolean )
at _81._10()
at _81._1(String , Object )
at _92._1(Object , ItemClickEventArgs )
at DevExpress.XtraBars.BarManager.RaiseItemClick(ItemClickEventArgs e)
at DevExpress.XtraBars.BarItem.OnClick(BarItemLink link)
at DevExpress.XtraBars.BarBaseButtonItem.OnClick(BarItemLink link)
at DevExpress.XtraBars.BarItemLink.OnLinkClick()
at DevExpress.XtraBars.BarItemLink.OnLinkAction(BarLinkAction action, Object actionArgs)
at DevExpress.XtraBars.BarButtonItemLink.OnLinkAction(BarLinkAction action, Object actionArgs)
at DevExpress.XtraBars.BarItemLink.OnLinkActionCore(BarLinkAction action, Object actionArgs)
at DevExpress.XtraBars.ViewInfo.BarSelectionInfo.ClickLink(BarItemLink link)
at DevExpress.XtraBars.ViewInfo.BarSelectionInfo.UnPressLink(BarItemLink link)
at DevExpress.XtraBars.Controls.CustomLinksControl.OnMouseUp(MouseEventArgs e)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at DevExpress.XtraBars.Controls.DockedBarControl.WndProc(Message& msg)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Here are the steps I took before getting the above:

1. Compared two databases.
2. Droped and rebuilt one of the databases while the app was up.
3. Hit the refresh button, but got a message that could not connect to one of the databases (as I later found password field for the rebuilt database was empty).
4. Pressed 'Ok' and got the exception.

Thanks.

Daniel Handley

Hi

I will make sure that the developers of the user interface see this message so that they can try to add in some additional error handling for this kind of situation.

Thanks
Dan

Tom Harris

Hi,

this has been fixed in development. The fix will be included in SQL Bundle 5.1. Bundle 5.1 will be released in May 2006.

Thanks,

Tom Harris

Red Gate Software