This looks more fundamental than a code bug. As far as John can see from the call stack it seems to be throwing an exception around the HTML control used to show the startup info, which then gets stuck in a loop in the Windows event processing, i.e. each time the exception gets handled, it finishes by telling Windows to process the next message which causes another exception.
Reinstalling Recorder is the only thing we can suggests. A potential concern is that something else on the machine has changed (e.g. a Windows update) that might have caused the problem.
Before doing this you must make sure you have backups of the Recorder 6 system, both the database and files.
Security - You need to secure the following
1. The whole of the Recorder 6 folder
2. The whole of the User File Folder.
3. We suggest that you take a backup of the database through R6 (If this will work). Also that you detach the database using Management Studio and then take a copy of NbnData_data.mdf and the associated log file.
Deleting Recorder 6
You should be able to uninstall Recorder 6 through control panel. If the problem you have prevents this then it can be deleted manually - if necessary please ask for further details on this.
Re-Install
1. Install version 6.23 which is available for download from http://www.recorder6.info/page16.html
2. Make sure this is working the detach the blank database using Management Studio.
3. Copy in the saved version of NBNData_data.mdf and the log file in to the data folder of SQL Server to replace the files already there.
4. Use Management Studio to attach these to the SQl server instance (http://www.recorder6.info/page12.html has instruction )
5. Upgrade Recorder 6 to version 6.25
6. Copy back in the contents of the User File folder. Keep the backup of all files just in case there are problems.
Mike Weideli