russellg Posted April 17, 2005 Report Share Posted April 17, 2005 When I try to export a selector, it prompts me for the filename, and then the program generates an assert log and crashes. Anyone else seen this problem? Russell Link to comment Share on other sites More sharing options...
AmyJ Posted April 19, 2005 Report Share Posted April 19, 2005 What version of Retrospect are you using? Do you have a selector within a selector? In other words, does the selector you are exporting contain a condition refering to another selector such as: selected by Movies Link to comment Share on other sites More sharing options...
russellg Posted April 20, 2005 Author Report Share Posted April 20, 2005 Hi Amy, I'm using the trial version of Retrospect 7.0 (version 7.0.3.101) on Windows XP Pro. No, not using a selector within a selector (didn't know you could do that actually). It appears to be just this one selector list -- it has about 30 or so lines in it, but even if I delete almost all of them, it still crashes the program when I try to export it. I tried copying it to another selector name, but it crashed too. I tried copying "C:\Documents and Settings\All Users\Application Data\Retrospect\config70.dat" to another machine, and the selector came up fine when I viewed it on that machine, but it still crashed Retrospect when I tried to export it. I called tech support, and they'd never heard of the problem. I emailed them my config70.dat and the crash report that's generated each time it crashes, and even told them the exact filename and line of code it crashed on (it's noted in the crash file), but the tech I talked to didn't sound overly concerned with it -- just said it was probably an isolated incident and that I should just recreate the selector :-( I did recreate the list, and it did solve the problem -- we'll see as to whether or not the info I submitted to them gets converted into a program fix. Isolated or not, programs should never crash while dealing with data (especially data they created themselves), programmers should always fix crash bugs (especially when a user reports the exact line of code it crashed on), and phone agents should be a bit more energetic about passing on crash report info from customers to programmers. Thanks, Russell Link to comment Share on other sites More sharing options...
AmyJ Posted April 21, 2005 Report Share Posted April 21, 2005 Hi Russell - I know there were a few issues with exporting selectors that contained other selectors which were fixed, but it sounds like your issue is a bit different. That said, I'm sorry your experience with tech support was not satisfactory. If there's a reproducible problem with the software I'm sure a bug will be logged. Take care, Amy Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.