v.3.5.2.1 UR-Win XP shutdown error

[ashwken]

From the thread:
http://www.kinook.com/Forum/showthre...&threadid=3086

Originally posted by kinook
Refreshing was the fix for the two bugs mentioned. But we found a way to fix the scroll bar issue without refreshing, and the latest download http://www.kinook.com/Download/UltraRecallProEval.exe has the improved fix.

Working with an Item (Type - Text) that has a Form containing three fields (Item Title, Text-1 Text-2 - both Text fields are Lookup List). The Item Detail Pane Body contains pasted text from an outside source.

The creation of these Items was a different work session.

Edit pasted text for each Item - populate the form's fields (from text in article), article formatting. Select next Item from Tree and repeat.

At some point - after a dozen or more Items have been edited - UR will produce a Windows program shutdown message (the one where you send a report to MS). Click on Don't Send and UR closes. Upon re-launch of UR the only data "lost" was the last edited Item.

I put up with this or a while (4-5 work sessions ending in this error message), then started to incorporate an explicit Save action when editing was complete, but before moving focus to the next Item to edit in the Tree (Data Explorer). This seems to help.


Ultra Recall Professional 3.2.5
Registered to: Kenneth Ashworth (1-user license)
Windows version: 5.1.2600.2.0
Install path: C:\Program Files\UltraRecall
EncryptPDF.dll version 3.0.0.2
mimepp.dll version 3.0.4
pdf2txt.dll version 3.1.0.4
PolarSpellChecker.dll version 4.0.5.4
SftPrintPreview_IX86_U_10.dll version 1.05
SftTree_IX86_U_50.dll version 5.06
UltraRecall.exe version 3.2.5.1
unins000.exe version 51.47.0.0
C:\WINDOWS\system32\MsftEdit.dll version 5.41.15.1514
C:\WINDOWS\system32\RichEd20.dll version 5.30.23.1228

[ashwken]

Originally posted by ashwken

I put up with this or a while (4-5 work sessions ending in this error message), then started to incorporate an explicit Save action when editing was complete, but before moving focus to the next Item to edit in the Tree (Data Explorer). This seems to help.

Well, not really, the error came back after about 5-dozen edits.