![nvivo 8.0 nvivo 8.0](https://i.ytimg.com/vi/QKKEqUbBMwA/maxresdefault.jpg)
Shiphra has emailed QSR regarding an issue converting an NVivo 7 project to NVivo 8 directly from a network drive which causes NVivo 8 to crash. You might be out of luck if you've done a lot on your project since converting it. And I was lucky that I hadn't done much coding before the problem started, so it didn't take long for me to re-do it. Not sure if that's your problem, but it seems to have fixed mine - at least for now. Now it seems to work fine with no more crashes! I opened NVivo 8, opened the Nvivo2 project on the hard drive and had it do the conversion there, then saved it as an NVivo8 project. So instead, I copied it (in Nvivo2 version) to my local hard drive. That old project was on a network drive, which I know can cause problems with NVivo. So I thought maybe something went wrong when I converted it from NVivo 2. Sounds like your problem project pre-dates NVivo 8, as did mine. I tried playing with the sample project that comes with NVivo8, and everything there worked fine, so I figured it might be a problem within my project. Hi - I've had the same (extremely frustrating!) problem recently and everything I tried in the help files didn't solve it - just kept crashing, over and over - but I think I found a solution. (Int32 dwComponentID, Int32 reason, Int32 pvLoopData)Īt .ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)Īt .ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)Īt .Run(Form mainForm)Īt .Program.b(String A_0)Īt .Program.c(String A_0) Other functionality seems to work OK (viewing sources, codes, even case attributes), but when I try to open the casebook, everything stops.Įxception = System.IndexOutOfRangeExceptionįullText = System.IndexOutOfRangeException: The column was not foundĪt .MatrixGridData.a(Int32 A_0)Īt .MatrixGridData.c()Īt .MatrixGridControl.f()Īt .MatrixGridControl.s()Īt .MatrixGridControl.a(MatrixGridData A_0)Īt .CasebookDetailForm.ah()Īt .CasebookDetailForm.a(EventArgs A_0)Īt .OnCreateControl()Īt .CreateControl(Boolean fIgnoreVisible)Īt .CreateControl()Īt .WmShowWindow(Message& m)Īt .WndProc(Message& m)Īt .WndProc(Message& m)Īt .WndProc(Message& m)Īt .WmShowWindow(Message& m)Īt .WndProc(Message& m)Īt .ControlNativeWindow.OnMessage(Message& m)Īt .ControlNativeWindow.WndProc(Message& m)Īt .DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)Īt .IntCreateWindowEx(Int32 dwExStyle, String lpszClassName, String lpszWindowName, Int32 style, Int32 x, Int32 y, Int32 width, Int32 height, HandleRef hWndParent, HandleRef hMenu, HandleRef hInst, Object pvParam)Īt .CreateWindowEx(Int32 dwExStyle, String lpszClassName, String lpszWindowName, Int32 style, Int32 x, Int32 y, Int32 width, Int32 height, HandleRef hWndParent, HandleRef hMenu, HandleRef hInst, Object pvParam)Īt .CreateHandle(CreateParams cp)Īt .CreateHandle()Īt .CreateHandle()Īt .get_Handle()Īt .SetVisibleCore(Boolean value)Īt .NVivoApplication.d(DetailForm A_0)Īt .NVivoApplication.bu()Īt .NVivoApplication.a(Control A_0, Object A_1, ToolClickEventArgs A_2)Īt .NVivoApplication.a(Object A_0, ToolClickEventArgs A_1)Īt .OnToolClick(ToolClickEvenĪt .FireEvent(ToolbarEventIds id, EventArgs e)Īt .OnToolClick()Īt .OnClick()Īt .DoClickProcessing(MouseĪt .OnMouseUp(MouseEventArgĪt (MouseEventArgs e)Īt (Object sender, MouseEventArgs e)Īt (Object sender, MouseEventArgs e)Īt (Control control, ProcessEvent eventToProcess, EventArgs e)Īt (MouseEventArgs e)Īt .OnMouseUp(MouseEventArgs e)Īt .WmMouseUp(Message& m, MouseButtons button, Int32 clicks)Īt .DispatchMessageW(MSG& msg)Īt .UnsafeNat
![nvivo 8.0 nvivo 8.0](https://docplayer.fr/docs-images/41/5969294/images/page_12.jpg)
![nvivo 8.0 nvivo 8.0](https://img.informer.com/pd/qsr-nvivo-v12.2-explore-tab.png)
Now each time I try to open the casebook, NVivo stops working and must close. I have about 100 cases and as I was adding information in the casebook, the program crashed. Have you had any luck in resolving this issue? I seem to be having the same problem and QSR Support's suggestions have not worked so far.