PDA

View Full Version : Access crash on listbox.removeitem



Movian
01-06-2016, 08:34 AM
Hey so another weird problem.

we have some machines in a clients office (Touchscreens on windows 8.1 64 bit) that are having a problem all other machines / clients are not having.

When the following function triggers


Private Sub lstFinalList_KeyDown(KeyCode As Integer, Shift As Integer)
If KeyCode = 46 Then
If MsgBox("are you sure you wish to remove this DX code?", vbYesNo, "confirm") = vbYes Then
Me.lstFinalList.removeitem (Me.lstFinalList.Value)
End If
End If
End Sub


Specificaly


Me.lstFinalList.removeitem (Me.lstFinalList.Value)

access has a hard crash to desktop, after checking the event logs it appears the problem is with a specific DLL file.

MSVCR90.dll - version: 9.0.30729.8387

which gives error code 0xc0000417

After a quick search I saw that Foxit phantom PDF was installed and was utelizing that dll and had office plugins attached but uninstalling foxit phantom PDF did not help..


any suggestions for where to look next?

~Edit - Complete event from log~
Faulting application name: MSACCESS.EXE, version: 14.0.4750.1000, time stamp: 0x4b8bade7
Faulting module name: MSVCR90.dll, version: 9.0.30729.8387, time stamp: 0x51ea24a5
Exception code: 0xc0000417
Fault offset: 0x000320f0
Faulting process id: 0x350
Faulting application start time: 0x01d1489428b9e330
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office14\MSACCESS.EXE
Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.8387_no ne_5094ca96bcb6b2bb\MSVCR90.dll
Report Id: 65516193-b488-11e5-8269-28c2dd4042d7
Faulting package full name:
Faulting package-relative application ID:

jonh
01-06-2016, 09:22 AM
Considering the syntax is RemoveItem(Index) I was surprised to find after a quick test that passing value instead actually does work.


But since Access must be doing some sort of jiggery-pokery behind the scenes to make it work and that this suggest a problem with the strcopy function (https://support.microsoft.com/en-us/kb/956420) on 64bit that it's likely using, I would suggest to provide it the actual index and see if that works.



lstFinalList.RemoveItem lstFinalList.ListIndex

Movian
01-06-2016, 09:52 AM
I made that change (haven't heard jiggery-pokery in some time!)

still crashing but different error this time..


The program MSACCESS.EXE version 14.0.4750.1000 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: 1c64
Start Time: 01d148a14f66a6f7
Termination Time: 5
Application Path: C:\Program Files (x86)\Microsoft Office\Office14\MSACCESS.EXE
Report Id: dbc88005-b494-11e5-8269-28c2dd4042d7
Faulting package full name:
Faulting package-relative application ID:

jonh
01-06-2016, 10:26 AM
Event logs don't seem to get any more useful do they?

Save the values into a table and manipulate that?

jonh
01-06-2016, 10:28 AM
Or try the hotfix

markecb
01-15-2016, 02:20 PM
A similar problem I had in case two copies of the office, for example, 2003 and 2007 or 2007 and 2013...