Hi Guys,
Our Order Processor emailed me today that SuperManager keeps crashing on him. I tried to get specific details, but his response was:
"It happens while processing orders, but it never happens at a similar event."
He then needs to redo everything he's done up until his last save.
Any thoughts/suggestions? I know this is really vague.... He mentioned it typically happens once per week, when he is in the midst of processing a group of orders (25+).
If there are additional details / files / etc I can provide you - please let me know.
jabrein,
Sorry this is happening to you. One thing you can relate right away...Generally when SuperManager closes unexpectedly it usually gives you a message like this:
QuoteUnknown error has occurred and SuperManager was forced to close.
Current database was saved to <file path>
To open this file re-open SuperManager and choose 'File' | 'Open...', change the file type to '*.sbk' and select this file.
When this message pops up you should be able to either open the folder where this file is stored in windows and double click on the file (usually Recovered.sbk) to open it in SuperManager - or you can do as it says to open it from within SuperManager. You should find that this recovered database has all the data as of the time SuperManager crashed. By opening this recovered database you can at least get back to where you were when it crashed.
As far as figuring out how to avoid this happening altogether...Actually getting his input on whether this recovered database is properly saved will be a good place to start. Also, it would be helpful to know what things he is typically doing when it happens would help. Is it when charging credit cards? Doing XML Exchange with DAZzle or WorldShip or another function? etc... I wasn't sure if when you said it happens while processing orders if that meant any or all of these activities, or just one or two of them typically.
Thanks,
David