Originally Posted by dbranch
|
I have this same problem. It was a project that I started in SI4 and imported it into 5. I have tried both of the fixes listed above and and have had no success. Tech supoort told me that They are aware of the problem but that there is no fix at this time. Unbelievable.
I have been a loyal D-Tools user since version 1.5 and have always been a supporter and fan despite the quirks and bumbs along the way. But I have gotta' say that this release is flat out useless. If I can't work on a project then what good is this software to me. I realise that any new piece of software is going to have bugs but that is what beta testing is all about. You don't release a piece of software for general use what it has this many problems. I am only talking about this problem right now but I have had many issues like everybody here and have wasted countless hours trying to fix or get around them. I am not saying that the product is bad because it has bugs, I'm saying that it shouldn't have been released until these problems were fixed.
The onlything I can sys is that it's a good thing I still have SI4 because I refuse to use 5 until it works - COMPLETELY
|
I feel your pain brother!
I finally had to uninstall D-Tools, Visio and .net 2 & 3 on seven different machines here in our office. Reinstall Visio, updates, reinstall .net (from the D-Tools discs only) reinstall D-Tools, more updates . . . you can imagine how many long evenings that took.
The removal of the .net updates is starting to impact other software that we run.
As of the last update I received from tech support, they still don't have a clue. I can only imagine the "wonders" that 5.2 will bring.
We haven't uninstalled 4.6 from most of the machines yet. We're seriously considering moving back to it for our new projects.