adccommunitymod (AutomationDirect) asked a question.
Created Date: September 16,2009
Created By: DCLittlejohn
**** This post has been imported from our legacy forum. Information in this post may be outdated and links contained in the post may no longer work.****
Directsoft has had and still does have (what I consider to be huge) problem with corrupting the documentation database if the program is not closed correctly (i.e. computer crashed) Why is it that only some of the documentation becomes corrupt? Why is it that reopening the file after the corruption brings back only some of the documentation, which seems random? Some old documentation that has been in there for a long time, and some of the newer documentation too? I am very disapointed that this problem has not been corrected by Automation Direct. Loosing an entire day to redo program documentation because of a minor computer crash is unacceptable. Yes, I have a backup from the previous day, but that does not have the documentation that I worked on yesterday. Even saving the project multiple time throughout the day does not protect someone from having this problem occur. Fix this problem.
Created Date: September 16,2009
Created by: franji1
We 're sorry about the situation. We have fixed most of the corruption problems, but there still may be some out there.
To minimize the possibility of corruption
1. Make sure you are running the latest DirectSOFT, Rel 5.3
2. Make sure any projects created before Rel 5.x have been "recreated " from scratch using Rel 5.3 using export/import program.
DirectSOFT creates backups passively, called "AutoSave " every time you save your program or project to disk, not just when you actively do a backup. Look in the Projects\Backup\AutoSave to possibly find a more recent copy of your project and element documentation.
If the files on disk become corrupted, there is nothing DirectSOFT can do after the fact.
Created Date: September 21,2009
Created by: Adisharr
I would also recommend changing your file name after each save so that if your current file gets corrupted you at least have your last uncorrupted file to work with.
Created Date: December 31,2009
Created by: kasky
Let me preface by saying I have been using Directsoft from the time of it's first release without a single problem.
Since I have installed 5.3 I have had / having trouble with corrupted documentation files. Stuff like giving a nickname to V3000 and it ends up in v3000 and v3001. Delete one and they both get deleted. "Infinite Loop " warnings telling me I may need to extend the loop time. Be nice to know how to do this as the software docs don't say a darn thing about infinite loops.
Any programmer out there knows how important the documentation is, if it were me I would not be so worried about including links to web sites and such and I would get the documentation problem fixed! :mad:
Created Date: December 31,2009
Created by: Tubecut
I have had similar issues in the past , but not on a large scale.
I have since learned to use the CNTRL-s keys and that seems to work great.
Also, mentioned earlier, use the export feature, a great backup.
Cheers
Created Date: September 16,2009
Created by: DCLittlejohn
Directsoft has had and still does have (what I consider to be huge) problem with corrupting the documentation database if the program is not closed correctly (i.e. computer crashed)
Why is it that only some of the documentation becomes corrupt? Why is it that reopening the file after the corruption brings back only some of the documentation, which seems random? Some old documentation that has been in there for a long time, and some of the newer documentation too?
I am very disapointed that this problem has not been corrected by Automation Direct. Loosing an entire day to redo program documentation because of a minor computer crash is unacceptable.
Yes, I have a backup from the previous day, but that does not have the documentation that I worked on yesterday. Even saving the project multiple time throughout the day does not protect someone from having this problem occur.
Fix this problem.