X   Site Message
(Message will auto close in 2 seconds)

Welcome to UtterAccess! Please ( Login   or   Register )

Custom Search
   Reply to this topicStart new topic
> Access Crashes On Truncated Text In Treeview Control, Access 2016    
post Aug 31 2017, 08:31 AM

Posts: 21
Joined: 7-May 17

I’ve been using treeview control on MS Access forms for years without problems. However, recently encountered a problem with forms that had been working fine but now crash Access under one circumstance:

The treeview control still works as designed except when there are nodes with truncated text that extend beyond the control’s right border. The moment I hover over one of those nodes (no mouse click, only hover), I get the system hour glass and 5 seconds later Access crashes without any explanation.

Here’s the system event log:
Faulting application name: MSACCESS.EXE, version: 16.0.8326.2076, time stamp: 0x598eafa5
Faulting module name: unknown, version:, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x3bec
Faulting application start time: 0x01d3224855506c73
Faulting application path: C:\Program Files (x86)\Microsoft Office\Root\Office16\MSACCESS.EXE
Faulting module path: unknown

System details:
MS Access 2016 (32 bit) running on Windows 10, 64-bit system
OLE Class: TreeCtrl
Class: MSComctlLib.TreeCtrl.2

On the attached image, I can click on any of the nodes with short text.
But when I hover over EX-B01.1A BELLOWS – COLD AIR TO HOT C…, Access crashes.

Any help or comments will be appreciated.
Attached File(s)
Attached File  treeview.jpg ( 75.7K )Number of downloads: 10
Go to the top of the page
post Aug 31 2017, 08:36 AM

UtterAccess VIP
Posts: 6,276
Joined: 30-June 11

I know there's been a serious issue because of a recent update that broken the common controls, including the Treeview control. Hence why I recommend not using it and instead using the 100% VBA TreeView (see: http://www.devhut.net/2017/06/15/great-acc...eview-control/). That said, try updating your installation to the latest build (8326.2096) and see if that doesn't resolve the issue. Fingers crossed.
Go to the top of the page

Custom Search

RSSSearch   Top   Lo-Fi    17th December 2018 - 07:32 AM