[Solved] Return of File column names not responding to mouse & Error 380

Hi David,

Sorry about the issue. Thanks for the screen shots and videos. So cool and helpful.

Perhaps I am missing it, but I don't see an example of clicking on dropdowns and column names not working. Can you provide a screenshot of just one example of this please? Provide enough context so I know what dropdown and what window you are clicking on.

In the final video, I do see the RTE 380, when attempting to load the View Sightings window.

This usually indicates invalid data saved in the Registry. The fix is usually to reset/clear all of this data. It is just data such as saved preferences, window sizes, etc.

Perhaps I should get onto your computer and have a look at this.

Please send an email to me at jeff@BirdersDiary.com to schedule a time. I am available off and on today, and then most of Monday.

Jeff

Hi Jeff,

The first video showed me higligthing and clicking on file name - nothing happened but with atl f  I could get File header up.

Just tried it - and the clicking on file name worked.... also just had a MS Win 10 update yesterday.

Dave

Update:

I was able to get onto David's computer today. All of his problems seem to stem from his Win10 computer signalling errors on SSDW3B32.ocx in the Event Viewer under the Application events folder. This is a 3rd party piece of software that BD has been using since the 1990s. 

BD currently hangs when David attempts to use the View Sightings Setup and clicks on the Continue button. The error is shown in an error window and then an Empty View Sightings window is shown that is non-responsive. At this point, he has to close BD in order to use other functionality. We are unaware of other parts that are affected, but everything else I tried seemed to work.

I tried the following, and none of it solved the problem.

• Renamed C:\Windows\SysWOW64\ssdw3b32.ocx and ran the v5.2.34 installer. This placed a new version of the OCX file on his computer; assuming the current one might be corrupt. This did not solve the problem.
• Ran a sfc /scannow on his system and it reported no errors.

To me this indicates an unstable system. We were able to reproduce this error every time, however, the System Event Log did not show the error logged every time.

David as Norton Antivirus and CCleaner programs on his computer.

He is now going to remove both programs and reboot. These programs are known to cause problems and this is worth a try. Windows Defender will auto-start protecting his computer once Norton is removed. He will then run the v5.2 installer and test.

If the above does not work, then he is going to run the Windows 10 Repair feature and try again.

We will report back here after all of this is tried.

Note: no one else is currently reporting this issue and I do not remember this ever being reported.

Jeff

Screenshot of the error from the event viewer on David's system.

Update: removal of Norton and CCleaner with reboot did not solve the problem. 

Next up: Run Windows 10 System Repair utility.

Update: Problem resolved!

I uploaded a debug version of BD to David's computer and located the problem. He had a corrupt Layouts51 Table in the MSAccess database. This information doesn't mean anything to anyone other than me should this problem occur again.

I resolved the problem by clearing all records from this Table and starting BD again. It detects an empty table and rebuilds the default layout for the Sightings View window.

Thanks to David for his assistance and patience in resolving this.

Jeff